Skip to main content
NEUS verifier schemas and the public catalog index live in this repo. A contributor opens a PR here to add a new check; once merged, the definition propagates to the protocol verifier registry. No private infrastructure access required.

​
Before you write code

Open a Discussion describing:
  • Who the check is for (buyer, integrator, agent builder).
  • What it proves (identity, ownership, permission, safety).
  • Inputs the integrator supplies. No PII. Deterministic for identical inputs.
  • Outcome the buyer sees (verified, processing, failed) and what it unlocks at a gate.
A reviewer will confirm whether the check belongs in the public catalog or is better handled by composing existing checks.

​
What a new verifier needs

All public artifacts live in this repo. The protocol picks up the verifier from here.

​
Conformance

A public verifier must:
  • Return deterministic outputs for identical inputs.
  • Carry no PII in inputs or outputs.
  • Document external API usage with rate limits and error handling.
  • Note gas or performance considerations if it anchors on-chain.

​
Submitting a PR

  1. Add the input JSON Schema at docs/verifiers/schemas/<id>.json.
  2. Add the catalog entry to spec/VERIFIERS.json with tier: "public", the schema path, flow, interaction, and API flags.
  3. Add a capability reference page at docs/verification/<id>.mdx and link it from docs/verification/verifiers.mdx.
  4. Update docs/openapi/public-api.json examples if the request or response shape changed.
  5. Add a [Unreleased] entry in CHANGELOG.md describing the integrator-visible change.
Run the public validators before requesting review:
The merged verifier is then wired into the protocol verifier registry.

​
What not to include

  • No wallet addresses or private env names.
  • No verifier outcomes that the live protocol does not return. Confirm from running code or tests before documenting a result.
  • No parallel verifier catalogs — spec/VERIFIERS.json is the single public index.

Verifier catalog

Current public checks.

Verifier schemas

Request shapes.

Signing format

How a request is signed.

Discussions

Propose before you code.
Last modified on August 13, 2026