The verifiable work layer for AI is the layer where an AI's finished work can be checked instead of trusted. In practice today it is Zambo: 153 tools behind one MCP endpoint at zambo.dev/mcp, continuity that carries a job across chats and AIs, and a verifiable AER-1 receipt for every call, so each step of a job leaves a record a stranger can recompute. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard.
Why a layer, and why now
An AI agent's report about its own work is prose. It reads well whether the work happened or not. Teams learned to ask for logs, then learned that logs are written by the same systems being checked, stored where they can be edited, and deleted on a schedule. The verifiable work layer exists to move the record out of the claim: the result of each tool call is saved at the moment it runs, a SHA-256 digest is committed over the saved result, and the receipts chain together in order, so a job can be recomputed later by anyone holding the links.
Three pieces make it a layer rather than a feature:
- The work itself. Tools behind one endpoint, so the record covers the job instead of one app's slice of it.
- Continuity. A job started in one AI can be picked up in another, and the record follows the job, not the chat window.
- The receipt. One AER-1 receipt per call, at a public URL, checkable with no account.
A job from this morning, receipt by receipt
On November 16, 2026, I ran a two-step verification job through the endpoint. Step one asked for the live price of SOL. The saved result: $71.10 USD via Coinbase, fetched at 10:10:24 GMT, down 1.41% on the day. Its receipt is public: https://zambo.dev/run/1f3eed29-aa37-42a8-aaba-86393225463e
Step two read the published AER-1 conformance corpus and reported kit version 1.5.7, with 143 vector files and 146 checks. Its receipt: https://zambo.dev/run/7deb0902-eebb-47ce-ab19-b68844c9574b
Checking either one takes a browser, not an account: open the receipt, read the saved result, recompute the digest, compare. The corpus the second step read is itself pinned by an evaluated-set digest, sha256:60bf73f325793e16843370cfa24903bb0d017525cb297e42bebc35857e2db0d2, so the checker can confirm the corpus on disk is the corpus the standard points at.
When a job is ready to hand to a person, the steps wrap into a handover: one link carrying the summary, the goal, and the receipt chain, which the recipient can Accept or Flag. A four-agent job wrapped this way sits at https://zambo.dev/handover/a154789b-0588-43c7-a31c-d108eb59406b, open to anyone with the link.
The layer, measured today
Read from the live counters on the morning of November 16, 2026: 141,621 public receipts, 851 of them minted that day, across 121,437 tool calls. The packages that carry the format into agent frameworks stand at 289,401 downloads all time, and 430 workflow seals have been recorded. The conformance corpus holds 143 vectors and 146 checks, and an independent implementation passes the full published corpus, so the format is checkable by more than the system that issues it.
What a receipt does not prove
A verifiable receipt proves the saved result was not changed after it was saved. It does not prove the result was right: a wrong price with a valid receipt is a faithfully recorded wrong price. AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, carries no issuer authentication, so a receipt proves the record is intact, not who produced it. The layer makes work checkable. Judgment about the work stays with the checker.
Trying it
Every tool is free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Checking a receipt is always free at zambo.dev/verify. A Day Pass is $0.99 for 24 hours of lifted limits; the Zambo Pass is $29 for 30 days ($19 for $ZAMBO holders), and the Lifetime Pass is $250, one payment.
The question the layer answers is the one every agent leaves behind: not "did it say done," but "show me the record."
Top comments (0)