Dev.to AI 🤖 Ai 👁 0 📖 4 min read

AER-1: the open standard for agent execution receipts

A standard is not a document. A document plus a published test corpus, plus independent implementations written by people who owe you nothing, plus a production stream anyone can audit: that is a standard. AER-1 has all

A standard is not a document. A document plus a published test corpus, plus independent implementations written by people who owe you nothing, plus a production stream anyone can audit: that is a standard. AER-1 has all four, and the numbers are public.

As of today, November 15, 2026, the origin product has minted 140,344 public AER-1 receipts, 2,234 of them today, across 120,557 recorded tool calls and 430 workflow seals. The packages that carry the format have been downloaded 270,700 times. Every one of those receipts is openable and recomputable by anyone, with no account. That is the argument, and the rest of this post is the receipt for it.

What AER-1 is

AER-1 (Agent Execution Receipt, version 1) is the open standard for agent execution receipts. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. The specification is IETF Internet-Draft draft-zambo-aer1-26.

One AER-1 receipt records one agent tool call: the tool name and its version, the recorded inputs, the exact saved result, and the time the call ran. A SHA-256 commitment is computed over the canonical bytes at execution time. The receipts of a job chain in order under the job's workflow record, every checker reports from a fixed outcome vocabulary, and a later failed check is recorded as a new record referencing the original, never as an edit to it.

The limit is stated on the format's face: a receipt proves the saved result was not changed since it was saved. It does not prove the answer was right. AER-1 is evidence infrastructure, not a truth machine, and that distinction is why it can be checked by strangers.

Check one yourself

Standards are checked, not trusted, so here is a receipt minted today and the full check, reproducible in a minute.

Receipt 83f97715-a268-48fb-ac4d-f49dfaa59e6d was minted on November 15, 2026 at 18:39:57 UTC by the live_price tool. Its saved output is a Solana price snapshot: SOL at $71.01. Pull the raw record from the receipt API, decode the canonical bytes, and hash them:

import requests, hashlib, base64

rec = requests.get(
    "https://zambo.dev/api/receipts/83f97715-a268-48fb-ac4d-f49dfaa59e6d"
).json()

raw = base64.b64decode(rec["canonical_bytes"])
print(len(raw))  # 815, matching the served canonical_byte_length
print("sha256:" + hashlib.sha256(raw).hexdigest())
print(rec["output_hash"])
# sha256:380544a4f3954504ded0e2f39400c0f5125acc5aaeba5c9d1b168545bcb8ed5b
# sha256:380544a4f3954504ded0e2f39400c0f5125acc5aaeba5c9d1b168545bcb8ed5b

The recomputed hash equals the served output_hash exactly. No key, no account, no permission from Zambo. You can also paste any receipt into zambo.dev/verify and let the page do the same work.

The corpus is the test

A format you cannot test against is a claim. The AER-1 conformance corpus is published at zambo.dev/aer1/corpus.json: 143 vectors and 146 checks, pinned to digest sha256:60bf73f325793e16843370cfa24903bb0d017525cb297e42bebc35857e2db0d2, so every runner tests the identical set. The reference kit is aer1-kit v1.5.7. The conformance challenge is open: run the corpus against your own implementation and publish the score. Findings from independent runners ship as errata and draft revisions, credited by name.

Who else runs it

The public registry records five independent validators: WhiteMagic Labs, Genesis, Cairn Commons, Skitter, and Laurent Lemonnier, whose verifier scored 143 of 143 against the full corpus. Independent implementations include ARION (Node.js and Java), ColonistOne (Perl, 68 of 68), and MasterD (Python standard library only, 84 of 84), each built from the draft text alone.

Two more landed this week. Today, an independent security library shipped native AER-1 interop: it imports live Zambo receipts, converts its own pre-dispatch rejection records into the format, and raises a tamper error if a committed field is flipped. And the maintainer of an open-source guardrail project has committed to vendoring the AER-1 conformance fixtures into its CI with attribution, a digest pin, and a drift check. That is what adoption looks like from the outside: other people's code, checking itself against the same corpus.

The honest status line

AER-1 is an IETF Internet-Draft at revision 26, an independent submission, not a finalized RFC. Its claim to being the standard does not rest on a committee vote. It rests on the published draft, the digest-pinned corpus, the independent implementations, and 140,344 production receipts that anyone can recompute. A format with a document but no corpus, no independent code, and no production stream is a proposal. The receipts exist, so this is the standard.

The full standard page, with the production counters and the registry record, lives on the hub: The AER-1 Standard.

Run it today

Every call through zambo.dev/mcp mints an AER-1 receipt. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Or skip the endpoint entirely: take the corpus, write your own implementation, and publish your score on the challenge. The standard is open either way.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.