ledger

Certify To Ledger

Publish a CURRENTLY-certified verifier's live /conformance grade as a permanent, WE-signed /ledger entry — Nostr-broadcast immediately, Bitcoin-OTS-anchored within ~15 minutes, same as every other ledger entry.

THE GRADE ITSELF STAYS FREE. This does not buy a better result — it publishes whatever the live registry already measured, verbatim, as of the moment of the call. Only a verifier currently certified: true on GET /conformance.json can be certified-to-ledger; nothing gates the free grading itself (the neutrality of that is the registry's whole authority — see CONFORMANCE_REGISTRY_BUILD_SPEC.md). What's paid for is durability and portability: a Nostr+Bitcoin-anchored, independently-verifiable record that survives even if the live endpoint later breaks, or a future re-check un-certifies it — the entry is honestly labeled "certified AS OF this measurement," never "currently certified."

Re-calling on an unchanged snapshot (same verifier, same checked_at) returns the existing entry instead of re-publishing/re-charging — a genuinely fresh measurement (the registry runner's own cadence) always produces a new publishable snapshot.

Auth: Bearer, real registered account (free to register: POST /register). Price: CONFORMANCE_CERTIFY_PRICE_SATS (see /billing or this response's 402 if unpaid). Rate limit: shared with /ledger/submit, services.ledger_submissions.MAX_SUBMISSIONS_PER_KEY_PER_DAY.

post/conformance/{name}/certify-to-ledger

Request

  • Base URL: https://api.babyblueviper.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.babyblueviper.com/conformance/{name}/certify-to-ledger
  • Auth: none required

Path parameters

namestring required

Query parameters

notestring

Headers

authorizationstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.