Anyone can check
Is this receipt real?
Try the sample. Change one field. Watch it fail. The check runs in your browser. No account, no download.
- Works in your browser
- No Aqta account
- Change one field, it fails
Sample Live check
Signed decision receipt
Sealclaude-3-7-sonnetPII redaction
7d8jZ-lDkwfUBfl-P2qLDfH1l1CHKu9czyLfviLjmRlu-uJ8SY_TrSkVUK0P3dGRBPXI8FDvlEAzOs92H4mzAAThis is the seal itself. Change any line above and it stops matching.
The call was permitted after policy evaluation.
Have your own receipt?
Retrieves the record. The signature check still runs in this browser.
A receipt is signed proof of exactly what an AI was cleared to do. It holds up when challenged. Anyone with the file can check it. You do not need us online.
What a receipt proves, and where it stops
It proves
- The holder of the published key signed exactly these fields
- Not one signed field has changed since
- Which policy was in force, and what it decided
- Which model was requested
It does not prove
- That the computation described is the computation that ran. A gateway signature proves what the gateway said, not what the compute did
- That the decision was correct, fair, or free of model error
- That every decision was recorded. One never written down leaves no trace of not having been written down
Those limits are ours, written up in full in our research note and threat model.
Or check it where you already work
Seal also ships as an MCP connector, ai.aqta/seal in the public registry, so a reviewer can check evidence inside the assistant they already use. Add https://app.aqta.ai/api/mcp, ask for a sample receipt, verify it, change one field, verify again. The first check passes. The second fails.
It reports whether the key was pinned by you or embedded in the record, and never treats those as the same claim. How it works.
Now see what a reviewer sees
One receipt is a file. What matters is the moment someone outside the company opens the evidence and decides. This is a real docket: two production decisions, one allowed and one blocked, checked in your browser, with the question fixed before the evidence was opened.
Open the sample review docketNo account, nothing sent to us.
For engineers
Checks run against whichever key the receipt carries, and the tool names it. The sample receipts here are signed with a demo key, so you can tamper with them freely; a production receipt is signed with Seal's published key, and the tool says so when it sees one. Paste your own JSON below, or run the reference verifier.
The checker on this page reads model-call receipts. An agent's tool action is a sibling record, ACTION-v1, checked with the same key by the reference verifier. Every record both formats define is published as conformance vectors, valid and deliberately broken, with the key to pin.