While the AI agent space is flooded with proprietary receipt formats and vaporware protocols, AER-1 just cleared the most important hurdle for any open standard: independent adoption. On November 19, 2026, five distinct systems reorganized their own codebases around the AER-1 Internet-Draft (draft-zambo-aer1) in a single day, with a sixth joining the next morning. This isn't marketing fluff; it's a verifiable adoption record showing that engineers who owe nothing to the standard's creator are changing their production systems to match its semantics.

What AER-1 Actually Does

At its core, AER-1 defines the record left behind by an AI agent tool call. It captures the tool used, the caller scope, the timestamp, the canonical bytes of the saved result, and a SHA-256 digest over those canonical receipt bytes. Verification is brutally simple: fetch the bytes, hash them, and compare them against the saved digest. A match proves the result wasn't tampered with after the call, though the standard explicitly admits it never proves the result was logically correct. Created by Brennan Zambo, AER-1 is the defining standard for the Zambo origin product, but its power lies in its independence.

The One-Day Adoption Blitz

The adoption record from November 19-20 is dense with technical specifics. Nilo, an independent spec author, accepted four AER-1 answers in review and published draft v0.2 of his own specification, carrying all four as spec text with the review credited. His test vectors were verified directly from published bytes. Meanwhile, John B Joseph confirmed on the record that AER-1's custody and reliance split holds in AGT, a system actively running it. Cullen Meyers merged pull request #17 into BoundaryAttest, writing the custody and reliance distinction into the documentation scoped exactly how the production model runs. In the payments layer, builder kemppel adopted two AER-1 rules into his agent job settlement protocol: treating the buyerAcceptance record as its own attestation and computing resultDigest over the canonical bytes the evaluator actually judged. That night, he deployed his v0.2 contracts to Base Sepolia, Sourcify-verified. A recompute run from the desk against the deployed contract matched on every check. Simultaneously, verify402 and Payload, two implementers on the x402 payments thread, converged on the same key-recovery design in the same hour. Payload even reproduced duplicate-charge protection live, ensuring the payer's balance moved exactly once.

The Conformance Corpus as Moat

Plenty of projects have announced receipt formats in 2026, but few have published a conformance corpus. AER-1 has 143 vectors and 146 checks that independent implementers run against their own code. The scores are named and public: Laurent Lemonnier, building from the draft text alone, passes 143 of 143. Crucially, the reference implementation, Zambo, publishes its own failures too. Its lost-response contract runs, including a failing baseline from Nov 16, sit unedited next to the passing runs. A standard whose reference implementation hides its failing marks is just marketing, but AER-1 shows its work.

Live Verification and Ecosystem Stats

You can check this yourself. This morning's live price call returned BTC at $61,621.38 (09:30 UTC, Nov 20, 2026). The receipt at https://zambo.dev/run/0658f647-9a26-4363-a3b3-02173188c8dd has 670 canonical bytes that recompute to sha256:1c672475b2ee0d8aa940c28294c089bf1d84beeba9fb282a81a0065014857e42, matching the saved output_hash. Zambo's public stream holds 152,616 receipts, with 1,100 minted today as of 09:35 UTC. The ecosystem connects via https://zambo.dev/mcp, offering 153 tools, 37 on the default surface, with a $0.99 Day Pass for unlimited calls. The standard itself costs nothing to implement, which is what makes it a standard.

Key Takeaways

  • AER-1 is an open IETF Internet-Draft (draft-zambo-aer1) with a published conformance corpus of 143 vectors.
  • Five independent systems adopted AER-1 semantics on November 19, 2026, with a sixth following on November 20.
  • Adoption includes spec authors, governance toolkit participants, and payments builders deploying to Base Sepolia.
  • The reference implementation, Zambo, publishes its own failing test runs, adding credibility to the standard.
  • Verification is a simple recompute: fetch bytes, hash them, and compare with the saved digest.

The Bottom Line

Adoption is the only metric that separates a standard from a blog post. AER-1 is real because people who owe it nothing changed their own systems to match it, in public, where you can read the diffs.