Checks a real mainnet record against the public Hedera mirror with zero requests to TenPrint; exit 0 means all five checks pass. Details in Rung 2 →
Read what the endpoint actually returns. No rendering.
Public, no key. Every signature result, every lineage link, every ledger timestamp — machine-readable.
Run the standalone verifier. Your machine checks it against the public ledger.
npx @tenprint/verify --example
Start here. --example checks a real mainnet record against the public Hedera mirror node. It pins the keys file bundled in the package automatically, so it needs no --keys flag, and the --example command makes zero requests to TenPrint. It runs five steps on your machine: the ML-DSA-65 signature, the leaf hash, the batch root, the aggregate root, and the anchor on the ledger. Exit code 0 means all five passed. Exit 1 means a step failed, and the output names it. Exit 3 means the record format is not supported, and 4 means the mirror or keys file could not be reached.
Then check your own records. Pass the record and the anchor bundle for its anchor:
npx @tenprint/verify --record record.json --anchor-bundle anchorId.json
When you check your own records without --keys, the tool fetches TenPrint's published keys file. With it, the tool uses only the file you give it.
What this does and does not prove. The example pins a keys file bundled in the package, so the signing key still comes from TenPrint unless you get the key through another channel and pass it with --keys. And the tool proves a record was attested and anchored. It does not prove the record's content is true.
Older records: npx @rubric-protocol/verify <attestation-id> is the legacy verifier.
@tenprint/verify on npm → Read the source on GitHub →Rebuild the Merkle chain yourself. Forty lines, no TenPrint code.
curl -sO https://tenprint.ai/docs/verify-apa.py
python3 verify-apa.py proof.json
Records are anchored in two hops: leaf to batch root, batch root to the aggregate root published on Hedera. This verifier reimplements both from the published specification — it shares no code with the node that produced the anchor — then reads the on-chain value directly from Hedera's public mirror node and compares. The only TenPrint input is the proof package, which anyone holding an attestation can hand you.
It also refuses to overstate. Anchors written before 2026-07-30 under tree version 2 bind the number of batches rather than their contents (RUBRIC-SEC-2026-001, found by writing this very tool). The verifier reports those as partial and exits non-zero rather than showing a green check. A verifier that cannot fail is not a verifier.
Run it against a sample anchor →If TenPrint disappeared tomorrow, your records stay checkable.
The signing keys are committed to a public ledger. The attestations are anchored to it with consensus timestamps no operator can rewrite. The verifier is open source. Records remain checkable against the public ledger without TenPrint.
Without --keys, the verifier downloads TenPrint's published keys file, which would not be available if TenPrint were gone. The file holds public keys only, so save a copy alongside your records each time you archive them and pass it with --keys to verify with zero requests to TenPrint. A copy saved before a key rotation will not cover records signed after it, so keep the copy current with your records.
The same limits from Rung 2 still apply. The signing key still traces to TenPrint unless you obtained it another way. And verification proves a record was attested and anchored. It does not prove the record's content is true.