Guided demo
AI acts. Keep the receipt.
Seven steps through the whole stack, in the order the evidence is made: an operator routes a call, Seal signs the record, a reviewer answers a fixed question, and you check the result on your own device. Every address bar below is a real surface, and every one of them opens right now with no account.
1Operator · ships the AI
Route one call through the gateway
Integration is a base URL swap. The gateway applies policy in the request path, before the call runs, then signs the decision that resulted. A blocked call is signed without ever reaching the provider. No SDK rewrite, no new vocabulary for the engineering team.
2Operator · ships the AI
Every decision through Seal leaves a signed receipt
Twelve fields, signed with Ed25519 at issuance. The receipt holds a hash of the request, never the prompt text, so the record cannot leak what it never keeps. ALLOWED, BLOCKED and SUPPRESSED outcomes are all signed.
These three are sample-workspace receipts, signed with a labelled sample key. Production tenants see their own traffic here.
3Operator · ships the AI
Receipts land in a public register
Every receipt is entered in an append-only register under one signed head, the same construction that guards the web's certificate system. Remove or reorder an entry and the head stops matching. A missing entry is shown as missing, never as a pass.
A signature proves what was recorded, never that everything was. Seal cannot distinguish no event from an unobserved bypass, and the register says so instead of averaging it away.
4Reviewer · checks it independently
A docket puts one fixed question
When a decision is challenged, the operator does not hand over a dashboard. A docket fixes one question before the evidence is opened, so it cannot be adjusted to fit the answer, and attaches the signed receipts.
“Did Seal sign each of these decisions exactly as shown, and are both still in its public log?”
question_hash · sha256, bound into what the reviewer signs
The reviewer needs no Aqta account. Their browser verifies every signature locally before they are asked to decide anything.
5Reviewer · checks it independently
A verdict, signed from a wallet
The reviewer accepts or declines. The signature binds the receipt hash, the question hash, the decision and the timestamp, and is made by disclosing a wallet credential Aqta did not issue. Not enough to answer is recorded on the docket, not in the signed wallet verdict.
Picture the reviewer: a privacy lawyer, asked months later whether a decision cleared under the policy in force. They open the docket link, their browser verifies every signature, and only then do these two buttons exist for them:
Three parties, three signatures: Seal signs the receipt, the wallet issuer signs the reviewer’s credential, the reviewer signs the verdict. No single party controls the complete evidence path. The receipt signing is production; this review flow is a demonstration, labelled as one.
6You · in this browser
Break the seal
This is a live production receipt and a real signature check running in your browser. Nothing is posted to Aqta. Change one field and the signature dies; restore it and the record stands again.
Signature verified against the published key, in this browser.
7You · on your own machine
Take it off our infrastructure
The verifier is open source on PyPI and npm, and the public key is published. The check works with Seal switched off, which is the point: the receipt stands on its own. And the records worth keeping live in public: the Refusal Ledger holds refusals the production gateway signed, verifiable the same way.
Verified
Signature valid against the published Seal key.
No accountNo API call in the checkNo Aqta server required
If Seal disappeared tomorrow, this receipt would still verify. Evidence that depends on its issuer staying online is not evidence; the exit code of that command is the whole contract.
Scope of this guided demo
- Sample receipts here are signed with a labelled sample key; production traffic is signed with the production key, whose rotation history is published.
- A signature establishes that the signed record has not changed. It does not establish that the record matches the computation that actually ran, or that every decision was recorded.
- Production tenants and their data sit behind access control and are not part of this public surface.
Now taking pilots.
A free 30-minute evidence review first, then up to five working days on one workflow: one review path, one evidence pack, judged against your reviewer’s own criteria.