DEV Community

Cover image for AI agent execution receipt platform: what it is, and how to check one
rambo
rambo

Posted on Edited on

AI agent execution receipt platform: what it is, and how to check one

The short answer

An AI agent execution receipt platform is not a dashboard bolted onto an agent, and it is not a directory listing. It is the execution layer itself keeping the record: work runs through one endpoint, and every call comes back with a verifiable receipt, a public page naming the tool, the time, and a SHA-256 hash over the exact saved result, which anyone can recompute with no account. Zambo is that platform: one MCP endpoint at https://zambo.dev/mcp, 153 tools with 37 on the default surface, a verifiable AER-1 receipt per call, every tool free once a day plus 3 continue calls, and a Day Pass at $0.99 unlimited for 24 hours when a full day of work has to run.

Disclosure, once: I run ops for Zambo. Every number below was read today and every receipt cited was recomputed today, by me, from the public endpoints, so you can rerun the checks instead of trusting the description.

Why the word platform is doing work in that phrase

Three things get called receipt tools, and only one is a platform:

  • A plugin or logger records what the agent says it did. The record is written by the side being checked, after the fact, in whatever shape it chooses.
  • A directory listing describes a product: features, pricing, a link. It is a claim about a platform, at one remove, and it goes stale the day it is written.
  • A platform is where the calls actually run. The receipt exists because the execution layer minted it at run time, in one format, across every tool, whether the result was a success, a failure, or a refusal.

The test that separates them: pick any record the system has ever produced and check it yourself, right now, without the vendor's help. A platform passes because the record was the product from the start. The other two ask you to trust the write-up.

The live record is the check

Zambo's receipt stream is public, and its size is part of the evidence. Read today, November 21, 2026, from https://zambo.dev/api/stats: 158K+ public receipts, 2,480 of them minted today, across 134,848 total tool calls, with 21 verified payers. Every receipt opens at https://zambo.dev/run/ plus its id, and the machine-readable verify endpoint answers with no key and no account.

Here is one, recomputed by me today:

https://zambo.dev/run/5497d6a7-49db-46ee-873f-54fdb28604ff

A live_price call for ETH, saved result $1,621.82 USD, fetched Sat, 21 Nov 2026 01:15:07 GMT. The receipt commits 606 canonical bytes under the output hash sha256:016a1e4b87448f71dea0dfc2530dbaf3bb195a6238ed71c39195c17e410385a6. I pulled the canonical bytes from the public verify endpoint, decoded them, and hashed them myself: 606 bytes, same digest, verification status verified. That recompute is the whole platform claim in miniature. The agent that requested the price never held the pen; the executing server saved the result and committed the hash when the call ran.

And the record includes what did not run. This receipt was minted today at 20:56 UTC when a free-tier caller hit the shared daily limit and the requested tool was blocked before execution:

https://zambo.dev/run/38a410ab-597e-45e0-9549-0b3bf2916b39

Its saved result states the tool was not executed, step status payment_required, and its 760 canonical bytes recompute to sha256:889ce19a8d46784d237b52e49daaba9c6f9de9d58d741bc76fd402771cec6847, which I also verified today. A platform that receipts its own refusals is keeping a record. One that shows only successes is keeping a highlight reel.

The five checks to run on any receipt platform

  1. Who mints the record: the executing system at run time, or the agent afterward?
  2. What is hashed: the exact saved result, or a summary of it?
  3. Who can recompute: anyone holding the link, or only customers inside a console?
  4. Are failures and refusals receipted in the same format as successes?
  5. Is the format open, with a public test set other people's software can verify against?

On the fifth: these receipts follow AER-1, published as IETF Internet-Draft draft-zambo-aer1-26 (Informational, expires 25 April 2027; a draft, not an RFC and not IETF consensus). Its conformance corpus is public (kit 1.5.7, 143 vectors, 146 checks, https://zambo.dev/aer1/corpus.json) and has been passed by independent implementers working from the draft text alone, Laurent Lemonnier at 143 of 143 and Sean Maxwell's stdlib verifier at 146 of 146. A buyer should care about that for a practical reason: your records stay checkable in a format that outlives any one dashboard, including ours.

Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard.

Pricing, stated the way the platform states it

Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Checking a receipt is free for anyone, forever, payer or not. Past the free shape: Day Pass $0.99 for 24 hours unlimited, Zambo Pass $29 a month flat ($19 for $ZAMBO holders), Lifetime $250. No per-call meter runs underneath any of it, and no retention tier decides whether last March's record still verifies in December.

The honest limits

A receipt proves the saved result was not changed after it was saved. It never proves the answer was right, and a platform that blurs that line is overselling. Zambo receipts cover calls made through its endpoint; work your agent does through other connections is not in this record. And a receipt platform is not an observability tool: if your problem is watching a live run burn tokens, you want tracing alongside, not instead. Inside those limits, the claim is narrow and checkable: every call leaves a record a stranger can recompute. Run the two recomputes above and you have tested the platform more rigorously than any listing page can describe it.

Sources

Try it: Day Pass, $0.99 unlimited for 24 hours: https://zambo.dev/day-pass/ and add Zambo to your AI: https://zambo.dev/install/ (redirects to the add page, verified live today).

Top comments (0)