What a new_session receipt records
A new_session receipt is one AER-1 record (receipt schema version 0.4, hosted profile zambo-hosted-receipt/1) for one call. Read from a real new_session payload, it records:
- Receipt id: a full UUID. The id is the address of the record: the human page is https://zambo.dev/run/ followed by the id.
- Tool: name
new_session, version4.0.0, scopepublic. - Timestamps: the record creation time, and inside the step list a started_at and a completed_at for the call itself.
- Step status: one step per call, with the tool name and its status. On the first example below the step status is
success. - The saved output: the exact output object the call returned, kept as canonical bytes. The saved output carries status, capture_enabled, instructions and a privacy_notice.
- Output digest: output_hash, the SHA-256 digest of those canonical bytes, with the canonical byte length recorded too (937 bytes on the first example below).
- Caller and provenance: a caller type (
sessionon the first example) and a provenance class ofEXECUTED BY ZAMBO, which states how the record was produced. - Declared side effects: the record declares its side effects,
noneon the first example. - Verification status: the API carries a verification_status field for the record. On the first example below, the verify API reported verification_status
commitment_matches, its wording for a record whose digest still matches the saved bytes.
Live new_session receipt examples
Each example below is a real new_session receipt. Open one and you see the saved result, when it was saved, and its digest, the same fields described above.
zambo.dev/run/385a0a96-cc05-4ac1-8431-ba2fddf8f9f4
Saved: 2026-10-24T10:40:47.542Z
Output SHA-256 digest: sha256:f5afebc832e66bcee0d71eb824c25667f5a35d4c06a0bede1369d09cb797c49b
Checked live on 2026-10-24: this URL returned HTTP 200 with this receipt on the page.
zambo.dev/run/baa01073-6f03-4e9c-af53-ebb54fb88054
Saved: 2026-10-24T06:35:17.060Z
Output SHA-256 digest: sha256:3f744c45d186c26076626bc2c4532a03232809e5285dd65698b4615767796199
Checked live on 2026-10-24: this URL returned HTTP 200 with this receipt on the page.
zambo.dev/run/0ecccbaa-ad1f-41d6-bff5-d6144d203a8e
Saved: 2026-10-24T00:30:45.533Z
Output SHA-256 digest: sha256:89fe81f694f767ad9e3aeee7489e4283c1af35bd8ad3fd28f9f31a43cf033148
Checked live on 2026-10-24: this URL returned HTTP 200 with this receipt on the page.
How to verify a new_session receipt
- Open zambo.dev/verify/ and paste the receipt link or the receipt id. The checker recomputes the SHA-256 digest over the saved bytes and reports whether the record still matches.
- Or call the API directly:
GET https://zambo.dev/api/v2/receipt/{receipt-id}/verifyreturns the record as JSON, including its output_hash and verification_status. - The format is AER-1, an open IETF Internet-Draft: draft-zambo-aer1-26. Anyone can implement the check; it does not need a Zambo account.
Verification answers one question: is this the record that was saved, byte for byte? It does not answer whether the result inside was right.
Get receipts for your own calls
Add Zambo to your AI once, at zambo.dev/add/, and every tool call after that files a receipt like the ones above. Every account starts with 20 free calls per day, and free calls file receipts too. The background is at AI agent receipts, and more worked examples are indexed at receipt examples by tool.