Verification · without an account

Verify a receipt

the same five checks as a receipt page · signature against the org key registry by kid · engine re-run · nothing is stored · the trustless path is the CLI on your own machine

Offline verify (CLI)

The bundleone JSON · ≤ 1.0 MB · a real one is ~2 KB

Drop the bundle here

.bundle.json — or choose a file below

verified in memory · never stored · never logged

Where a bundle comes fromyou were handed it, or you took it

« Download the bundle » on any receipt page/verify/<receipt id> → /api/receipt/<id> · the share link the org sent you
bundles[i] of an evidence pack/api/evidence?from=&to= from the org chain page · one JSON per receipt
tensoryard compute --out b.jsonthe CLI writes the same shape it verifies

Drop a bundle to see its verdict

The same five checks as a receipt page, re-run in memory. Nothing is stored.

Reproduce offlinethe same verdict, on your iron

tensoryard verify bundle.json --pubkey <kid>.pem   # → VERIFIED | REJECTED
# --pubkey = the key from the org's Public key page, compared to your contract

This page is a convenience, not the proof. It re-runs the checks on our servers and stores nothing ; the proof is the same command on a machine we do not control.