You can slap verifiable execution onto an AI agent in an afternoon using a vendor SDK, but what you get is a record format locked inside one company’s walled garden. If that vendor pivots, sunsets, or paywalls their endpoint, your audit trail dies with them. Real verifiability that outlives a vendor requires an open standard, not a proprietary library. Enter AER-1, an IETF Internet-Draft that defines exactly how an AI agent tool call leaves a verifiable, independent receipt behind.

The Anatomy of an Open Receipt

AER-1 (draft-zambo-aer1, revision -26) specifies a record containing the tool name, caller scope, timestamp, canonical result bytes, and a SHA-256 digest over those bytes. Verification is brutally simple: fetch the bytes, hash them, and compare against the saved digest. A match proves the record is intact, though the standard is explicit that this does not prove the result was logically correct. The reference implementation, Zambo, built by Brennan Zambo, includes a public conformance corpus of 143 vectors and 146 checks. This corpus is the critical piece vendor SDKs skip, allowing anyone to build a verifier from the draft text alone and grade their implementation against a shared standard.

Adoption Happens in the Trenches, Not Press Releases

Standards don't gain traction through marketing; they win when independent systems reorganize around them. On November 19, 2026, five separate systems adopted AER-1 principles in a single day. Laurent Lemonnier achieved a full 143/143 pass on the corpus using only the draft text, proving independent verifiability is possible without vendor help. Simultaneously, Nilo published a spec incorporating AER-1 answers, while John B Joseph and Cullen Meyers integrated the custody and reliance split into the Microsoft agent-governance-toolkit and BoundaryAttest respectively. Kemppel deployed v0.2 contracts to Base Sepolia with a verified resultDigest rule, and verify402 and Payload converged on key-recovery designs that passed live double-charge guards. By the next morning, Shikhyy had updated his spec to adopt the canonicalization profile.

The SDK Trap and the Independent Check

The core question for any agent developer is whether their verifiability is portable. If a competitor’s verifier cannot check your record without your vendor’s library, you are locked in. If the record cannot be checked after the vendor disappears, you have a liability, not an asset. AER-1 was written specifically so the record survives the garden. The Zambo public stream currently holds 152,616 receipts, with 1,100 minted on November 20 alone. Every single one is checkable at zambo.dev/verify with no account required, using a standard hash function you already own.

Key Takeaways

  • AER-1 is an open IETF standard, not a proprietary SDK feature, ensuring records outlive vendor relationships.
  • Independent verifiers like Laurent Lemonnier’s prove that you can build compliant tools without vendor libraries.
  • Adoption is driven by real-world integration, with five systems adopting AER-1 principles in a single day in Nov 2026.
  • Verification is a simple SHA-256 recompute, making it accessible to anyone without special hardware or accounts.

The Bottom Line

Stop buying verifiability as a subscription. Build against the open standard, or accept that your audit trail is just another line item in someone else's P&L.