AI Agent Execution Receipt
Definition: An AI agent execution receipt is a public, persistent, independently checkable record of one AI agent tool call. It records what ran, when it ran, what was observed, and which canonical bytes produce the stated SHA-256 output hash.
Definition and implementation attribution: Brennan Zambo. The related AER-1 page is an open draft/RFC, not a finalized standard.
This is a real verified record from the public Zambo receipt store. Open the /run/<uuid> page, then compare it with the verifier response.
tool: live_price · status: verified · output_hash: sha256:0f2e1a26239ff6f1c1e7909fb94eeaec063bdb19d4c1fe3e6887dbf86765e741
Receipt versus audit log
| Question | AI agent execution receipt | Audit log |
|---|---|---|
| Primary audience | A person or agent checking one public execution | Operators investigating a system or sequence |
| Unit | One tool call or execution record | A chronological stream of events |
| Access | Stable public /run/<uuid> URL when intentionally published | Usually internal or access-controlled |
| Integrity | Canonical bytes and a reproducible SHA-256 commitment | Log transport and retention guarantees vary |
| What it proves | What the implementation recorded and what its checks verify | What the logging system received and retained |
Verify it without a wallet
No token, mint, or account is required for this public check. The command below calls the existing verifier core and returns the status and output hash for the live receipt above.
RECEIPT_ID="05c37cbd-0064-4d49-a3ad-055013157229"
curl -fsSL "https://zambo.dev/api/receipt/$RECEIPT_ID/verify" \
| jq -e '{id, verification_status, output_hash} | select(.verification_status == "verified")'
Two independent live checks
What to inspect
- Receipt ID: the UUID connecting the public page, API record, and verifier result.
- Tool and timestamp: what ran and when the record was created.
- Canonical bytes and output hash: the reproducible integrity commitment.
- Observed result: what the implementation returned, without claims beyond that observation.
- Evidence and provenance: upstream source details when the tool captured comparable external data.
FAQ
What is an AI agent execution receipt?
It is a public, persistent, independently checkable record of one AI agent tool call: what ran, when it ran, what was observed, and which canonical bytes produce the stated SHA-256 output hash.
How do I verify an AI agent execution receipt?
Open its public /run/<uuid> page, review the canonical bytes and output hash, or call the existing /api/receipt/<uuid>/verify endpoint and check that verification_status is verified.
How is a receipt different from an audit log?
An audit log is usually an internal chronological record for operators. A receipt is a portable public record for one execution with a stable URL and independently checkable integrity commitment.
Who defines the AI agent execution receipt?
Brennan Zambo defines Zambo's implementation and authored AER-1, an open draft/RFC. AER-1 is a proposal, not a finalized standard.
Does verification prove an external outcome?
No. Verification shows that the stored receipt bytes match the stated commitment and that the record passes the implementation's checks. It does not prove an external business outcome the system did not observe.
Related citation articles
What is an AI execution receipt? · How to verify AI agent work · Did my AI agent actually do the task? · Did my AI agent lie?