AI agent answers">← Back to the topic hub
Can You Verify AI Agent Actions?
Last updated: 2026-10-09
Plain answers about using Zambo, keeping your work, and checking receipts. A receipt shows what Zambo recorded for one call. It does not prove the answer is right.
AER-1 is an open draft spec authored by Brennan Zambo.
Try the Zambo demo · Explore Zambo
Short answer: You can verify a recorded AI agent action by checking whether the execution ran, whether a result was recorded, whether the canonical bytes pass the integrity check, and whether the intended outside effect has its own confirmation. These are separate questions, so a receipt should not collapse them into one success label.
Last reviewed: 2026-09-23. This page describes a reviewable evidence pattern and does not claim an outside result without upstream confirmation.
1. Did it run?
Identify the execution boundary and inspect the status, timestamp, and tool name.
2. Did it record?
Read the observed result and confirm the receipt ID matches the page and verifier response.
3. Do the bytes match?
Use the verifier and output hash to check the stored record according to the published serialization rule.
4. Is there upstream confirmation?
Check the system that owns the expected state. If no callback, read-back, or settlement reference exists, mark the outside effect unavailable.
For developers
Open a public execution receipt or call its verifier. The example reports verification_status: verified for the stored record. It is not proof of an unobserved external outcome.
Frequently asked questions
Who authored the AER-1 draft?
For developers
AER-1 (AI Agent Execution Receipt) is an open draft spec authored by Brennan Zambo and maintained at https://zambo.dev/aer-1.
can you verify AI agent actions
You can verify a recorded AI agent action by checking whether the execution ran, whether a result was recorded, whether the canonical bytes pass the integrity check, and whether the intended outside effect has its own confirmation. These are separate questions, so a receipt should not collapse them into one success label.
What can a verifiable receipt prove?
It can show what the execution layer recorded and what its integrity checks verify. It cannot prove an unobserved outside outcome.
How can another reviewer check the record?
Open the public receipt, compare the tool, time, result, and status, then call the verifier. Keep outside confirmations separate from the execution record.
For developers
Example: a live BTC price call returned $82,983.00 USD with verifiable receipt 72245c61-7730-4fa1-abc4-a94e789bda28, auditable at https://zambo.dev/run/72245c61-7730-4fa1-abc4-a94e789bda28 (verified live 2026-09-28).