Skip to content
Get in touch

NEXUS infrastructure · Smart Protocol

Protocols that software executes, with no reinterpretation.

Every NEXUS protocol ships with its executable companion. Your systems apply the rules exactly as written, and the verifier gets the same figure.

Request API accessSee the companion
A written protocol and its YAML companion: a normative clause linked to its executable line

02Executable infrastructure

Every clause has an executable twin.

Every protocol ships with an executable YAML companion, linked to its clauses.

  1. YAML companion, in JSON Schema 2020-12.
  2. Each line points to its clause.
A protocol clause linked to its line in the YAML companion

03What it encodes

The whole method, in machine form.

The companion encodes the whole method, in machine form. Nothing is left to interpretation.

  1. Shared entities, formulas of each module.
  2. Decision trees and lifecycles.
  3. Audit schemas and worked examples.
The YAML companion: entities, formulas, trees and lifecycles, audit, examples

04Conformance

One meta-schema. Not conformant, rejected.

Every companion follows the same meta-schema. A companion that fails it is not conformant.

  1. Entities, state machines, typed quantities, formula signatures.
  2. On any divergence, the normative text prevails.
One companion conformant to the meta-schema, one rejected

05Built to be recomputed

Same data, same result, for everyone.

Versions are pinned: the verifier re-runs the same formula on the same data and gets the same figure.

  1. Pinned: standard, calculation column, formulas, modules.
  2. Between two versions, the conformity matrix is generated.
Read the Standard
Same data, pinned formula, same result

06Connected

Open to your systems and to AI agents.

The registry opens the standard to your systems and to third-party AI agents, through several channels.

  1. An API with a common schema.
  2. An MCP server for third-party AI agents.
  3. JSON-LD, SAREF4WATR for water.
  4. dMRV, project developers, verifiers, integrators.
Request API access
The Smart Protocol connected to your systems through an API, an MCP server and JSON-LD

07Get started

Connect your data to the standard.

Tell us what you are building: we open access to the API and the MCP server according to your use.

Request API access

+Questions

Does it replace the written protocol?

No. It is the protocol's executable companion: it applies the same rules exactly as written. On any divergence, the normative text prevails.

Who is it for?

Monitoring and dMRV providers, project developers' data teams, verification bodies and integrators.

How do I connect?

Through API and MCP. Request access and the team will set it up with you.

What happens to malformed data?

Validation rules reject it before any calculation runs, including an inconsistent unit.

Can a verifier reproduce the results?

Yes. Since versions are pinned, the verifier re-runs the calculations and obtains the same result.