How do I add AER-1 receipts to an AutoGen agent?
Install the aer1-autogen adapter, mint an AER-1 receipt where each agent's consequential step finishes, and verify the first receipts against the kit's conformance vectors. In a multi-agent system the receipts earn their keep fast: when agents disagree about what happened, the step record, not the transcript, settles it.
AutoGen systems converse their way to results, which makes their failure mode this cluster's recurring one: fluent, conflicting reconstructions of the same run. The adapter's job is to pin the run down while it happens. Each selected step, an agent's tool use, a hand-off, a delivered artefact, mints a receipt committing to the caller, the tool, the output, and the side effects, in the AER-1 format (IETF Internet-draft-zambo-aer1-21; kit version 1.5.4).
Follow the kit's IMPLEMENTING path for the byte-level rules, and gate the integration on its conformance vectors. Multi-agent systems add one selection problem the single-agent pages do not have: conversational steps are numerous and mostly cheap. Mint receipts for state changes, external calls, artefacts, and hand-offs; let pure discussion ride on the transcript, which is what transcripts are for.
The operating payoff appears at the first disagreement: instead of comparing two agents' summaries, you walk both against the step list, and the first departure is the bug. The sibling page on agent disagreements in this file works that method in full; this page is the wiring that makes the method possible.
Quickstart: AER-1 receipts for AutoGen agents
1. Install: pip install aer1-autogen. 2. Attach the adapter where your agents are constructed. 3. Select minting points: tool calls with side effects, external calls, artefacts produced, hand-offs between agents. 4. Run a short multi-agent task with at least one hand-off. 5. Verify: the kit's conformance vectors pass; one live receipt checks at https://zambo.dev/verify/ . 6. Runbook entry: package version, kit 1.5.4, minting-point rule. A vector disagreement at step 5 stops the rollout until the wiring is fixed.
Worked example
The conformance anchor is the kit's published fixture, receipt 130da435-e157-498e-af90-605866a86a27, reproduced by independent implementations from the draft alone. Your AutoGen wiring is correct when its receipts verify against the same vectors those implementations pass.
Frequently asked questions
Should every agent message mint a receipt?
No. Conversation is cheap and mostly internal; receipts are for steps with consequences outside the chat: state changes, external calls, artefacts, hand-offs. Selective minting keeps the record readable and the costs sane.
Can the agents read the receipts themselves during a run?
Yes, and well-built systems do: an agent handed a disputed claim can check the step record instead of asking the other agent, which is how multi-agent systems stop arguing and start debugging.
Does the adapter work with our own receipt storage?
Yes. AER-1 is an open format; the kit mints receipts you can store wherever your system keeps records. The hosted connection is the alternative for teams who want handovers and client checks included.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai