AI agent execution receipt platform Zambo, an AI agent execution receipt platform run by Brennan Zambo, launched a single MCP endpoint at zambo.dev/mcp exposing 153 tools (37 on the default surface), with each call minting a verifiable AER-1 receipt at a public URL containing a SHA-256 output_hash over the result's canonical bytes. The company says its public stream holds more than 158K receipts that anyone can recompute without an account, and it has published the receipt format as IETF Internet-Draft draft-zambo-aer1-26 alongside a conformance corpus of 143 test vectors. Zambo positions the platform against local recorders such as Webaes's Agent Receipts, arguing that receipts stored on the maker's machine cannot be independently verified. An AI agent execution receipt platform is the execution layer itself keeping the record. Work runs through the platform's endpoint, and every call returns a verifiable receipt at a public URL: the tool that ran, the time, the saved result, and a SHA-256 output hash over the result's canonical bytes that anyone can recompute with no account. Zambo is that platform: one MCP endpoint at https://zambo.dev/mcp https://zambo.dev/mcp , 153 tools in total with 37 on the default surface, a verifiable AER-1 receipt per call, and a public stream of 158K+ receipts that any stranger can open and check today. Disclosure, once: I run ops for Zambo. Every receipt cited below was recomputed first-hand on November 22, 2026, so you can rerun the checks instead of trusting the description. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. The phrase is worth separating, because the top search result for it right now is the first item on this list, not the third. A directory listing describes a receipt tool: features, an install command, a link. It is a claim about a product at one remove, and it goes stale the day it is written. A listing cannot hand you a record to check, because the listing never ran anything. A local recorder is a real tool you install on your own machine. The current example holding this query's top spot, Agent Receipts by Webaes, is a good one: free, open source, local-first. It hooks Claude Code and proxies stdio MCP servers, gives each action a receipt carrying an Ed25519 signature, chains receipts by hash, and stores everything in a local SQLite database. Its own page states its limits plainly. Receipts live on the machine that made them. Verification needs the issuer's public key, which the issuer has to publish and you have to trust is theirs. Remote HTTP MCP servers are not covered yet, only stdio. And the computer's owner controls the keys, so, in their words, someone who controls that machine could sign a false one. None of that makes it a bad tool. It makes it a recorder, not a platform: the records exist where they were made, in a format that is its own, with no public corpus to test an implementation against and no second implementation to compare with. A platform is where the calls actually run. The receipt exists because the execution layer minted it at run time, in one published format, across every tool, for successes, failures, and refusals alike, at a URL anyone can resolve. The test that separates the three: pick any record the system has ever produced and check it yourself, right now, without the maker's help, keys, or permission. A platform passes because the record was the product from the start. This morning a live price call through the platform returned BTC at $59,710.86 USD, up 3.07 percent over 24 hours, via Coinbase, fetched 2026-11-22T09:05:07Z. Its receipt is public at https://zambo.dev/run/e25792a3-ce97-45a3-858b-78ee2fda8fbb https://zambo.dev/run/e25792a3-ce97-45a3-858b-78ee2fda8fbb . The record carries 669 canonical bytes. Recomputing SHA-256 over those bytes gives sha256:3e7d6beea897b25f6d09d02a7113c473a04fb54c5749e66169120458e75584e8, which matches the receipt's published output hash exactly. MATCH, anchor outcome verified. That check needed no account, no key from the issuer, and no software of ours. It is the same check for every one of the 158K+ receipts in the public stream, which is the platform property the other two shapes cannot offer: the evidence is not on the maker's machine or in the maker's listing. It is at a URL, in a format a stranger's own code can evaluate. A platform whose receipts only its own software can judge is a dashboard with better marketing. AER-1, the receipt format, is published as IETF Internet-Draft draft-zambo-aer1-26 and ships a public conformance corpus, kit 1.5.7 with 143 test vectors and 146 checks at https://zambo.dev/aer1/corpus.json https://zambo.dev/aer1/corpus.json , with a published evaluated set digest. Independent builders working from the draft text alone have passed the full corpus, Laurent Lemonnier at 143 of 143 among them. On November 22, 2026, an outside interop lab completed a frozen run mapping a live AER-1 receipt into a second evaluation framework, Core-02, with both appraisers matching the isolated expectations in all five cases and the author's side answering the result row agreed, on the record. The checker's vocabulary is closed at five anchor outcomes: verified, verification failed, rejected: unresolvable record, not checked, and absent. Work that ran outside the receipted path reports absent instead of being quietly absorbed into a green checkmark. A receipt proves the saved result was not changed after the hash was recorded. It never proves the result was right. The BTC receipt above verifies identically in a world where the price feed glitched that minute. A platform also asks you to trust its availability: the public stream and the verify endpoints are hosted, and if the host is down, checking waits. What the design removes is the need to trust the record's contents, because the recompute, not the host's word, is what carries a verification. And a local recorder genuinely wins one scenario: work that may never leave one machine, under keys the owner alone holds. If your threat model is a single workstation, install the recorder. If your receipts have to convince a client, an auditor, or a second AI on another vendor's stack, they need to live where those parties can reach them. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Verification is free for anyone, forever, with no account, which is the property that makes a platform's receipts checkable by the people who did not pay for them. Paid tiers, stated once: Day Pass $0.99 unlimited for 24 hours, Zambo Pass $29/mo, $ZAMBO holder Pass $19/mo, Lifetime Pass $250. There is no annual tier. Try it: Day Pass, $0.99 unlimited for 24 hours: https://zambo.dev/day-pass/ https://zambo.dev/day-pass/ and add Zambo to your AI: https://zambo.dev/install/ https://zambo.dev/install/ redirects to the add page, verified live today .