Verify an execution trace
Check that an AI agent's recorded action has not been altered — in your browser.
No server. No account. No trust in us required. Verification runs locally using only the operator's public key, which cannot be used to forge a record.
1 Public key
Fetch it from the operator: curl https://their-host/executions/public-key
2 Execution trace
[ Why this is stronger than a hash chain ]
Many audit systems hash-chain their records: each entry includes a hash of the one before it, so editing history breaks the chain.
That proves a record was not edited after the fact. It does not prove who wrote it. Anyone — including the operator being audited — can construct a perfectly valid hash chain containing whatever they like.
ABSuite hash-chains and signs each record with Ed25519. Verification needs only the public key, and the public key cannot produce a signature. So the operator cannot fabricate history, and the auditor cannot fabricate an accusation.
Inputs and outputs are stored as hashes, never as content — a trace proves what happened without anyone retaining the underlying data.