Verify a Decision Receipt

Paste a Decision Receipt JSON below to inspect its structure, recorded replay status, policy result, and attestations. No account or API key is required; signer identity still depends on a key established out of band. A valid result concerns the receipt record and does not prove that the described action occurred or was correct.

Two samples, on purpose. Load a Real Receipt pulls the newest entry from the public ledger — it is genuine and it passes. Load Synthetic Invalid Sample is fictional and uses a placeholder signature; it is expected to fail. Seeing both is the point: a verifier that cannot fail tells you nothing when it passes.
Offline verifier security notice: JavaScript CLI 0.1.0/0.1.1 and Action 0.1.0/0.2.0 are withdrawn. The current published replacements are CLI 0.1.4 (d6763fdc…4c31, 21,275 bytes) and Action 0.2.3 (39b50ef6…2ed4, 28,388 bytes). They reject malformed Ed25519 trust keys, no longer report unsigned legacy cross-receipt linkage as PASS, and refuse repeated JSON object keys and integers outside the exactly-representable range at every JSON parse, including the pinned keyring. CLI source 0.1.5 is unreleased. CLI 0.1.2/0.1.3 and Action 0.2.1/0.2.2 are superseded but remain fetchable. Read the exact hashes and relying-party limitations.
Do this without our server, within the published limits. This page runs checks on our server, so you are still taking our word for the result. The Python offline verify kit checks defined signed content under independently established Ed25519 key material. Read its version and compare its SHA-256 with independently authenticated release metadata before use. Source version 1.3.1 accepts the canonical active/retired registry and applies lifecycle to signed generated_at; unsigned chain position remains UNVERIFIED. Source availability does not establish publication. Python 1.3.0 remains available at its immutable versioned URL and Python 1.1.0 is retired. The replay kit re-executes a decision and reproduces its hash. No install, account, or network is required after download. Neither proves key ownership, source truth, action execution, policy correctness, legal admissibility, regulatory acceptance, or unsigned chain position.