Verify a signed receipt_
Designed to start at Ready.
Verification runs in your browser. The receipt body never leaves this page.
How receipts work
When a billing event closes — a session ends, a training job finishes, or a readiness probe fails — the control plane signs the receipt body with Ed25519. The signing key is identified by its kid; the corresponding public key is published in the key archive at /trust/keys.json.
Verification is offline-capable: paste the receipt JSON above, fetch the archive once, and check the signature locally. Every rotation is counter-signed by the prior key (LEGAL-4 key custodian policy), so the chain of custody is auditable end-to-end.
The trust-claim line above is the canonical statement: failed readiness, training, or inference zero every line item on the receipt. The signature is the proof.