ZAMBO.

Your agent did a job. Where is the receipt?

The agent reports back: done. There is no record of what it ran, what came back, or whether the summary it gave you matches either one. On Zambo, every tool call files a verifiable receipt at call time, automatically. This page runs one real job live, shows the receipt it produced, and checks that receipt in public, so you can see exactly what a first agent receipt looks like before you generate your own.

The receipt from the job below: zambo.dev/run/c1f11a14. Check it free at zambo.dev/verify, no account needed.

Published October 25, 2026. The worked example was run live against https://zambo.dev/mcp the same day, and the verification result below was read back from the public verify endpoint.

The job, step by step

Scope, stated once: an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right.

  1. Search first. The session opened with a capability search for "generate a verifiable receipt for work my AI agent just did". The search ranked handover first, zambo_check second, and workflow_close third: the tools that open, check, and close a body of agent work. Searching first is the standing first move, because the right tool for the job is usually not the one you would have guessed.
  2. Run one real job. The job picked for this page is a live price check: the live_price tool returned BTC at $80,392.00 USD, via CoinGecko, at Sun, 25 Oct 2026 22:27:47 GMT. A small job on purpose. The receipt mechanics are identical for a price check and for a week-long workflow.
  3. The receipt files itself. The call produced receipt c1f11a14-b0d9-4b73-a0ad-75e4e711b8e8 at call time. No export step, no log to dig out, no screenshot. The receipt link is part of the call result.
  4. Check it. The public verify endpoint for that receipt returned verified, read back at 2026-10-25T22:33:21Z. Anyone can repeat the check: open the receipt, or paste its id at zambo.dev/verify.

What the verified result actually checked

The verify endpoint runs named checks against the saved record and reports each one. For this receipt, at check time:

  • Commitment: the saved result bytes recompute to the recorded sha-256 digest, sha256:b75da34fc667cf3b7cb16ffab0ebb96212827fa1fb64e2744d472b71c8ef6151. Pass.
  • Canonical form: the receipt is in the canonical AER-1 encoding, so independent tools read the same bytes the same way. Pass.
  • Provenance: the receipt's origin fields are present and consistent. Pass.
  • Metadata: the tool, timestamp, and caller fields match the saved record. Pass.
  • Issuer authentication: reported as not checked. The public endpoint does not authenticate the issuer, and the receipt says so instead of implying otherwise.

The receipt format is AER-1, specified by the IETF Internet-Draft draft-zambo-aer1-26, so the checks above are not a Zambo-only ritual: independent implementations run the same conformance corpus against the same record shape.

What this receipt proves, and what it does not

It proves the saved result was not changed since it was saved. If anyone edits the record of that price call later, the digest stops matching and verification fails. The number on the receipt page today is the number the call returned on October 25, word for word.

It does not prove the price was right. If CoinGecko had returned a wrong price, the receipt would faithfully preserve a wrong price, and verification would still pass. The receipt settles the argument about what the call actually returned. Whether the answer was good is still your review, or your second source. Anyone who tells you a receipt proves the work was correct is selling you the one thing a receipt cannot do.

Is there an AI agent receipt generator?

Yes, and it is not a separate tool you run after the fact. On Zambo the generator is the call itself: connect an agent to https://zambo.dev/mcp, make any tool call, and the receipt exists from that moment, with a public link. The companion guide, get a receipt for AI work, covers how to capture proof while the work runs; this page is the worked example that shows one receipt end to end, from the job to the check.

Receipts also file for calls that fail or get rejected, so the record covers attempts, not just successes. A refused first call still opens the receipt set; only no attempt at all leaves no record.

Get your first one

  1. Add Zambo to your AI at zambo.dev/add. One MCP endpoint, https://zambo.dev/mcp, 153 tools total, 35 on the default surface, no account and no API key to start.
  2. Make one call. A price check, a web search, a memory save: anything. The receipt link comes back with the result.
  3. Open the receipt and check it at zambo.dev/verify. You are now holding the same proof this page is built on.

Calls start issuing receipts right away, 20 free calls per day to start. A Day Pass is $0.99 USDC on Base for 24 hours of full access. The Zambo Pass is $29 for 30 days, one payment, with an annual option at $290.

Questions, answered

How do I generate a receipt for work my AI agent did?

Connect the agent to the Zambo MCP endpoint at https://zambo.dev/mcp and make a call. The receipt is filed at call time and the response carries its link; there is no separate generator step and nothing to export. Open the link any time to see exactly what the call saved.

What does verified mean on a Zambo receipt?

It means the saved bytes of the result recompute to the same sha-256 digest recorded when the call ran, and the receipt's canonical form, provenance, and metadata checks pass. A verified receipt proves the saved result was not changed since it was saved, not that the result was right. Issuer authentication is reported separately and is marked not checked on receipts from the public endpoint.

Do rejected calls get receipts too?

Yes. Every call files a receipt, including calls the server rejects. A refused first call still opens the receipt set; only no attempt at all leaves no record. That is what makes the receipt stream a complete account of what an agent tried, not just what succeeded.

What does it cost to get agent receipts?

Nothing to start: 20 free calls per day, each with its own receipt. A Day Pass is $0.99 USDC on Base for 24 hours of full access. The Zambo Pass is $29 for 30 days, one payment, with an annual option at $290.

Related

Run your first job free

Run your first job free. Get your own receipt in seconds. Everything this page describes is one call. This is the fastest way to make the receipt yours instead of an example.

Open Zambo Chat in your browser, run a real call, and keep the verifiable receipt it returns. Or paste this first call against the MCP endpoint:

curl -s -X POST https://zambo.dev/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"live_price","arguments":{"symbol":"BTC"}}}'

The response carries your first verifiable receipt in _meta under dev.zambo/receipt, with its public run link. Check it free at zambo.dev/verify, with no account. A receipt proves the saved result was not changed since it was saved; it does not prove the work was right. When one job becomes every job, a Day Pass covers 24 hours for $0.99, and ongoing use is the Zambo Pass at $29 for 30 days as one payment, or $290 for 365 days.

Then connect your own AI once. Add Zambo to your AI and every job after this one leaves the same kind of receipt, no pasted commands needed.