There is a sentence people are starting to say to their AI, and to each other:
"Get me a zambo receipt."
It means the same thing it means everywhere else in life. Do not tell me it happened. Show me the receipt. When an AI agent finishes a job, a zambo receipt is the record that job leaves behind: what ran, what it was given, and the exact result it produced, captured at the moment of execution and checkable by anyone, forever, without asking the agent to remember or explain itself.
This article is strictly about that record. What a zambo receipt is, what is inside one, what it proves, what it honestly does not prove, and how you get one.
What a zambo receipt is
A zambo receipt is a verifiable execution receipt. It is minted by the system that ran the call, at the moment the call runs, not written up afterward by the agent that did the work. That distinction is the whole idea.
An agent's summary of its own work is a claim. It can be wrong, incomplete, optimistic, or invented, and it is stored wherever the agent feels like storing it. A zambo receipt is evidence instead: a structured record of one execution, produced by the execution layer itself, bound to the exact bytes that went in and the exact bytes that came out.
Every successful call through Zambo leaves one. The receipt gets a permanent public page and a machine-checkable verification endpoint, so the person who ordered the work, the person paying for it, and a stranger auditing it three weeks later all look at the same record.
Inside a zambo receipt
A zambo receipt records the execution, field by field:
- What ran. The tool or function that executed, by name.
- What it was given. The recorded inputs, plus a digest of those inputs, so a swapped input shows up as a mismatch.
- What it produced. The actual observed result, saved in full, plus a SHA-256 digest of the exact output bytes.
- When. A timestamp from the moment of execution.
- The receipt itself. A unique identifier and a public run page where anyone can read the full record.
The digest is the working part. Verification recomputes the hash from the saved output bytes and compares it to the digest in the receipt. If a single character of the saved result changed after the fact, the recompute fails and the receipt says so. The record cannot be quietly edited later, by the agent, by the platform, or by you.
What a zambo receipt proves, and what it does not
The claim stays narrow on purpose, because a receipt that claims everything proves nothing.
A zambo receipt proves that the saved result is the result that came back when the call ran, unchanged since it was saved. It proves which call ran, with which inputs, in which order, and what came back.
It does not prove the answer was right. It does not prove the agent understood the task, picked the best tool, or told you the truth about the world outside the call. A receipt is not a grade and it is not a judge. It is the difference between "the agent says the email was sent" and "here is the record of the send call, its inputs, and what the service returned, check it yourself."
That narrowness is why the receipt can be trusted. It never reaches past what it can show.
Receipts for a whole job, not just one call
Real work is rarely one call. An agent researches, drafts, checks, sends, and files, and the question at the end is about the whole run: did all of it happen, in that order, with nothing quietly dropped in the middle?
So zambo receipts chain up. The steps of a job each leave their own receipt, and the job closes with a summary receipt that binds the step receipts together under a single root digest. Change one step after the fact and the root no longer matches. The whole run can then be sealed, which freezes the bound record of the step receipts as one finished package: one link you can hand to a client, a teammate, or an auditor.
The gaps show up too, and this matters more than people expect. A builder recently set a team of bots loose on an overnight task. They completed the first step and then did nothing for five hours, silently, and the owner found out by waking up and asking them. With a receipt per step, that night reads differently: step one is in the record, and then there is a five-hour hole where the rest of the steps should be. The absence is visible in the record instead of discovered by interrogation.
How to check a zambo receipt
Checking one takes seconds and requires nothing from the agent.
Open the receipt's public page and read the full saved output for yourself, including the empty fields when a call returned nothing. Or use the verification endpoint, which recomputes the digests and reports whether the record still matches what was saved. Anyone can do this. The agent does not need to be online, cooperative, or even still exist.
How to get zambo receipts
If you are a person, the fastest way to see one is the live demo: https://zambo.dev/demo/ It runs a real call in about ten seconds and mints a real zambo receipt you can check on the spot. No signup.
If you build with agents, Zambo connects over MCP at https://zambo.dev/mcp, and every call your agent makes leaves a zambo receipt automatically, on Claude, ChatGPT, Gemini, Cursor, and the other major clients, and through frameworks like LangChain and CrewAI. The format behind the receipt is AER-1, an open IETF Internet-Draft (draft-zambo-aer1-19, https://datatracker.ietf.org/doc/draft-zambo-aer1/19/), so the record your jobs produce is a portable format defined by an open Internet-Draft, not a proprietary screenshot trapped in one app.
If your bots live on Grok, the Zambo Receipt Bot (https://zambo.dev/receipt-bot/) collects, verifies, and files a zambo receipt for every job they do and sends you a nightly digest of links.
The habit
Receipts won in the physical world because they ended arguments. Nobody debates what the register recorded. AI work is reaching the same point: too much of it happens out of sight, at machine speed, for "trust me" to survive contact with a real failure.
So the habit is simple. When an AI does work that matters, say the sentence.
Get me a zambo receipt.
Your AI said "done." For $0.99, prove it: the Day Pass keeps every call receipted for 24 hours, no subscription, no setup. https://zambo.dev/day-pass/
Top comments (0)