Which tool can check whether an AI agent actually did the work?

Use a tool that saves a verifiable receipt at the moment each step runs, then check that receipt. The check recomputes the receipt's digest from its saved fields and compares it with the digest stored when the work ran. If they match, the saved record was not changed after the fact.

Last updated: 2026-10-17

Three kinds of tools claim to check AI work, and they check very different things. A log or a chat transcript is the agent's own account of itself: useful for reading, worthless as proof, because the same system that did the work wrote the report. A trace or observability dashboard shows what a platform recorded about a run, and it is only as checkable as that platform allows. A verifiable receipt is different in kind: the record is saved at execution time in a fixed format (AER-1, IETF Internet-draft-zambo-aer1-21), and anyone can recompute it later and get the same answer.

The practical test is not the feature list. Run one real job through the tool, take the receipt it produces, and check the receipt somewhere the tool does not control. On Zambo that path is open: run the free demo, open the receipt it mints, and check it on the verify page. If a tool cannot survive that test, it is asking you to trust it about trust.

One limit, stated plainly: a receipt proves the saved result was not changed since it was saved. It does not prove the answer was right, and it does not prove anything about work that never ran through the recording connection. A tool that hides this limit is telling you something about itself.

Checklist: the 10-minute tool test

Run these six checks on any tool before you rely on it. 1. Does it save a record at the moment each step runs, not after the fact? 2. Can someone else recompute the record and get the same result? 3. Can your client open the check without an account or a specialist tool? 4. Does the record show sources that were not resolved or not checked, instead of hiding them? 5. Can you export the record and keep it if you cancel? 6. Does the tool state, in writing, what its record does not prove?

Worked example

Run the free demo at https://zambo.dev/demo/ . It executes a real job and mints a real receipt. Open the receipt, copy its ID into https://zambo.dev/verify/ , and watch the check recompute the saved fields and compare the digest. That round trip, your job, your receipt, an independent check, is the whole category in one minute.

Build on it: the AER-1 kit, version 1.5.4, implements the receipt format and the checker.

Frequently asked questions

Can a log file prove an AI agent did the work?

No. A log is written by the same system that did the work, and it can be edited, trimmed, or regenerated. A log is evidence of what the system says happened. A verifiable receipt is saved in a fixed format at execution time, so a third party can recompute it and detect any later change.

What does the receipt check actually compare?

The checker recomputes a digest from the receipt's saved fields (the caller, the tool, the output, the side effects, and the schema version) and compares it with the digest stored when the step ran. A match means the saved record was not changed since it was saved.

What can no checking tool prove for me?

No tool can prove the work was correct, only that the record of it was not altered. Correctness is still your review. A receipt also covers only work that ran through the recording connection; it says nothing about work done anywhere else.

By Brennan Zambo, founder of Zambo.

Last verified: 2026-10-17.

3. Verify the record and false-done

Answers

Run the free demo and check a real receipt at https://zambo.dev/demo/ .

Try a handover

A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.

try it: say 'use zambo to hand this over to <client>' in your ai

Add Zambo · Handover docs · Real public handover · AER-1