Skip to main content
Public check schemas and the catalog index live in this repository. Open a pull request here. After it merges, the check appears in the live catalog. You do not need access to Proofable infrastructure.

​
Before you write code

Open a Discussion describing:
  • Who the check is for (a person, an app, or an agent).
  • What it proves (identity, ownership, permission, safety).
  • Inputs the integrator supplies. No PII. Deterministic for identical inputs.
  • Outcome the user 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 check needs

​
Conformance

A public check 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 verifiers/schemas/<id>.json.
  2. Add the catalog entry to verifiers/VERIFIERS.json with tier: "public", the schema path, flow, interaction, and API flags.
  3. Add a guide page at verification/<id>.mdx and link it from verification/verifiers.mdx.
  4. Update openapi/public-api.json examples if the request or response shape changed.
  5. Add a [Unreleased] entry in CHANGELOG.md describing what builders will see.
Run the public check before requesting review:

​
What not to include

  • No wallet addresses or private env names.
  • No outcomes the live API does not return. Confirm from running code or tests before documenting a result.
  • No second catalog. verifiers/VERIFIERS.json is the 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 September 14, 2026