Direct answer
The Proof Chain
Most AI work is delivered as a summary you have to trust. A proof chain is the opposite: the finished job arrives as one link, every step underneath it carries a verifiable receipt, and the person receiving the work checks the steps themselves before they accept. This page collects real, public chains from zambo.dev so you can open each one and run the check with your own hands, free, with no account.
Updated November 13, 2026. Every link on this page was opened and read on the day it was added.
Chain 1: a swarm job, wrapped for its owner
The job: a market scan where three assets were checked by three workers, with the results combined into one shared record. Three separate agents did the steps; the owner receives one link, not three summaries.
The chain: zambo.dev/handover/22034b4c-d782-4c33-8138-ae7bbd824a14 lists 6 steps with verifiable receipts, status pending, 6 checked and 0 not checked. The wrap that created it is its own receipt: zambo.dev/run/0c6299d8-b1d3-4917-b351-1d53717af336.
What to notice: the receipts prove the saved results were not changed since they were saved. The handover page says so itself, in its own header: receipt bytes only, not accuracy. That honesty is the product. The owner still judges the work; they just judge it on a record nobody quietly edited on the way to them.
Chain 2: a gated workflow, sealed by its receipts
The job: a two step workflow run on November 13, 2026, where each step was a prompt shield scan recorded as it ran, at 11:27:28 and 11:27:30 UTC.
The chain: zambo.dev/workflow/10402cc4-49d2-43af-a24e-922d92ba0eb4 groups its 2 receipts (receipt ids beginning 33ed21f5 and a4ad0ea1) under one page and publishes the SHA-256 Merkle root of the pair, so the set itself, not just each step, can be checked for changes.
What to notice: a workflow page is the mid job form of the same idea. Steps land as receipts while the work runs; when the job is done, the wrap-up handover is the form built for a human decision.
Chain 3: the two decision states, side by side
Open: handover bd7e5325 is a finished job still waiting on its client. The steps and receipts are all in the packet; the only thing missing is the decision, and the record says exactly that.
Accepted: handover 45434a17 is an end to end audit handover a client accepted, and the acceptance minted its own receipt on the record, with who decided and when.
What to notice: payment conversations change when both states look like this. An open handover is a named person owing a named decision on named steps. An accepted one is the release point, recorded, not remembered.
How a proof chain gets made
Step 1: connect your AI to zambo.dev/mcp, one endpoint with 153 tools in total and 37 on the default surface. Step 2: run the job there, so each call saves its result and returns a verifiable receipt as a byproduct of the work, not as extra paperwork after it. Step 3: when the job finishes, wrap it: one free wrap-up handover per day pulls the goal, the steps in order, the outputs, and the open items into a single link. Step 4: send the link to the person who owns the decision. They open it with no account, recheck any receipt free at zambo.dev/verify, and accept or flag on the record. The guides that walk each part: the freelancer client handover, the agency client handover, and what an AI handover is.
Why the wrap is where the sale happens
A single receipt proves one step. Nobody pays an invoice off one step. The wrap is the moment the whole job lands in front of the human who holds the wallet: the client, the owner, the person who asked for the work. That is why the free tier is shaped the way it is. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. A short job wraps free. A long job that outgrows the free day mid work is finished, not abandoned: a Day Pass at $0.99 makes calls unlimited for 24 hours, so the job completes and the chain reaches the person who can pay for it. Regular delivery work is the Zambo Pass at $29 for 30 days, $19 for $ZAMBO holders, and Lifetime is $250 once.
Run your next client job so it can be checked, not just described. Add Zambo to your AI, run the work, and send the wrap. If you are the one receiving AI work, send this page to whoever delivers it and ask for your next delivery in this shape.
Send this to your client
The page above is the reviewer view. The delivery itself takes twenty seconds: when the job wraps, paste this into the message you already send with finished work, and fill in the handover link from your own wrap.
Done. Here is the saved record of the job, step by step: [your handover link]. Every step opens its own receipt, and you can check any of them here, no account needed: https://zambo.dev/verify/. Each receipt proves its saved result has not changed since it was saved, and the chain shows what ran, in order, so you can judge the work itself.
From this morning's live run, a filled-in example reads the same way with https://zambo.dev/handover/22034b4c-d782-4c33-8138-ae7bbd824a14 as the chain. A client who can check the saved results stops asking for status updates, because the record is open instead of described.
Whose chain format this is
The chains on this page are AER-1 records: the receipt format written by Brennan Zambo, the founder of Zambo, and implemented by Zambo's tools on every call. That is why each step above opens a record a stranger can recompute, instead of a screenshot the producer controls.