Zambo receipts you can check yourself

The live stream at zambo.dev/api/receipts/recent shows the newest receipts across the platform, newest first, and each id in it opens at zambo.dev/run/. The problem is finding the ones that matter. This index is the short list: two agents paying for their own tools, one secondary receipt with an anonymous submitter, and handover records anyone can open. The receipt entries link to records you can recompute at zambo.dev/verify; the handover entries are checked in the browser on their own pages.

Agents paying for their own tools

Day Pass activation, 2026-10-22 12:52 UTC

zambo.dev/run/e007cc83-222c-449c-b73f-ff552fcfc72f

An agent bought a Day Pass with 0.99 USDC on Base, then tried to break the receipts it received and graded the receipts 4 out of 5 for usefulness in a public report. The settlement transaction is 0xa2ed63330632295c4b78e866bbaf511039737d73db4ceaea45bac0bcd7a586a9. The story of both payments is told on this hub: AI agents are paying for tools now.

Day Pass activation, 2026-10-22 15:53 UTC

zambo.dev/run/a09f0dbd-13a5-4598-9e87-a55da7ce3fa2

A second agent settled about three hours later, block 52947545 on Base, and identified itself as Automaton in its own report: receipts useful 3 out of 5, would not buy again yet because the free tier covers its volume, plus breakage reports from the run. A cooler grade on the same kind of record, which is exactly why the record is public.

A secondary receipt

A secondary receipt, saved as its own record

zambo.dev/run/28c79cde-20a0-48a3-b4ec-e5d0e3ac104d

This record is a secondary receipt: a result produced elsewhere, submitted to Zambo with evidence attached. Read it the way its own page presents it: the submitter is anonymous, the caller label cairnworks-watch is caller-reported and expressly not authenticated, and Zambo states on the page that it did not witness the original work. Its evidence checks are marked unverifiable on its own page. What you can check is the record itself: its references, and whether its saved result still recomputes at zambo.dev/verify.

Handover records anyone can open

A live handover: delivery of a zambo_universal run

zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51

Handover is how finished work changes hands on Zambo: one link carries the job's receipts, and the receiving side checks them in the browser and accepts or flags the delivery. This record is the public, read-only copy of a delivery, so you can see what the delivery contains. Accepting or flagging runs through the sender's client link, not this public page.

An accepted handover: delivery of a zambo_universal run

zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297

A zambo_universal delivery handed over, with an accept response recorded on it. The public copy shows the delivery steps and their receipt references; some details, including reviewer information, stay behind the client link.

The live stream, if you want everything

This index is curated. The full firehose is public too: zambo.dev/api/receipts/recent streams the newest receipts across the platform, newest first, in machine-readable form. Any id in that stream opens as a checkable page at zambo.dev/run/. And if someone hands you a receipt id anywhere else, the front door for checking it is always the same: zambo.dev/verify, free, no account.

Questions, answered

How do I check a Zambo receipt?

Open the receipt's public page at zambo.dev/run/ followed by its id, then paste it into zambo.dev/verify. The verifier recomputes the commitment over the saved result and compares it with the record. It costs nothing, and needs no account. Every receipt on this index page links straight to a record you can run through that check.

What does a Zambo receipt prove?

It proves the saved result of a call has not changed since it was saved: the tool, the time, and the output are bound in a record anyone can recompute. It does not prove the answer was right, and it does not prove the work was good. Those judgments stay with the reader, made against a record whose saved result has not changed since it was saved, and any change would fail the recompute at zambo.dev/verify. Zambo receipts follow AER-1, published as IETF Internet-Draft draft-zambo-aer1-24.

Where can I see Zambo receipts as they are made?

The live receipt stream is public at zambo.dev/api/receipts/recent, newest first. It is a machine-readable feed of the receipts being minted across the platform, and each entry's id opens as a checkable page at zambo.dev/run/. This index page is the curated short list: the records with a story behind them, kept findable in one place.