The badge, in one paragraph
The short answer
Verified with AER-1 is the embeddable badge for any builder or service whose work ships with a verifiable AER-1 receipt attached. It tells the reader one thing: this sender's deliveries carry a public record anyone can open and re-check, without an account and without trusting the sender. It is a claim about how the sender works, and the claim is checkable on every single delivery, because each delivery's receipt is right there to open. Zambo is the verifiable work layer for AI, and the receipts follow AER-1, an open format published as an IETF Internet-Draft (draft-zambo-aer1-23). AER-1 is an Internet-Draft, not a finalized standard.
That is the whole badge. Small on purpose: it sits in a README, a profile, or a service page without shouting, and it carries its weight because of what sits behind it.
What the badge means, and what it never means
What it means
The sender ships receipts. Work from this builder or service goes out with a verifiable AER-1 receipt attached: the job's steps, the saved results, and a digest a stranger can recompute, on a public link. A client who doubts a delivery does not have to argue about it. They open the receipt and check.
What it never means
The badge is not a verdict on a job. It never means Zambo verified, approved, or endorses a specific delivery, and it must never be placed so it reads that way. A receipt proves the saved result was not changed since it was saved; it does not prove the work was correct. The only honest claim about a specific job is the one that job's own receipt supports when someone checks it. That is why the embed patterns below always pair the badge with the delivery's own receipt link wherever a specific delivery is being presented.
Embed it: the exact snippets
Two places the badge works. On your profile, README, or service page, it states how you work. Next to a specific delivery, it works only alongside that delivery's receipt link, in the per-delivery pattern. Copy either form exactly; the link target is part of the meaning.
Markdown (README, profile, docs)
[](https://rambozambodotdev.gitlab.io/aer1-hub/ai-agent-verification-badge.html)HTML (site, service page, marketplace listing)
<a href="https://rambozambodotdev.gitlab.io/aer1-hub/ai-agent-verification-badge.html"><img src="https://rambozambodotdev.gitlab.io/aer1-hub/verified-with-aer1.svg" alt="Verified with AER-1: this work ships with a verifiable AER-1 receipt" width="146" height="20"></a>The per-delivery pattern (beside a specific job)
<a href="https://rambozambodotdev.gitlab.io/aer1-hub/ai-agent-verification-badge.html"><img src="https://rambozambodotdev.gitlab.io/aer1-hub/verified-with-aer1.svg" alt="Verified with AER-1" width="146" height="20"></a>
Delivered with its receipt: <a href="YOUR JOB'S RECEIPT LINK">check this delivery</a>Swap in the receipt link for the job being delivered. That pairing is the honest form: the badge says the sender works this way, and the link lets the client confirm it for this job, right now, free.
One distinction worth knowing: a single receipt also has its own per-receipt badge, which renders that record's live checked state. Use that one on the deliverable itself. Use Verified with AER-1 for the sender: the profile, the README, the service page.
A live delivery that carries one
Worked example: an independent service, receipts wired into its deliveries
Cairnworks, an independent agent studio, wired AER-1 into its standing-check deliveries: when the service delivers a check, the delivery carries a Zambo receipt of the secondary_receipt kind, recording the evidence submitted and the checks run. One of those deliveries is public and live: receipt 28c79cde-20a0-48a3-b4ec-e5d0e3ac104d, saved October 18, 2026, carrying the delivery's own record (inner receipt 79335193-6663-4e0c-b2a1-6d84bd331b9c). The receipt page states at the top that the result has not changed since it was saved, shows the commitment checks underneath, and states its own limits in plain words: the submitting service's claims are recorded as claims, and the receipt covers the record, not the correctness of the underlying work.
That is exactly the posture the badge certifies. Not "trust this studio." Instead: here is the delivery, here is its record, check it yourself, including the parts that do not flatter it. Any client of any service wearing this badge can do the same with any delivery. Checking takes seconds at zambo.dev/verify and costs nothing.
Who is eligible
- Implementations on the registry. If your implementation is listed on the official AER-1 registry, it passed the conformance kit, and the badge is yours. Not listed yet? Run the kit against your build and claim your row on the registry page.
- Services that ship receipts with their deliveries. If your service's work goes out with AER-1 receipts attached, the way the worked example above does, the badge states a fact your clients can check on any delivery. That is the qualification, and it re-tests itself every time you deliver.
If your work does not ship with receipts yet, the badge is the finish line, not the starting point. Attach receipts to your deliveries first: the live demo mints a real one in seconds, and how to verify an AER-1 receipt shows what your clients will see when they check. Then come back and embed it.
Questions, answered
What does the Verified with AER-1 badge mean?
It means the sender's work ships with a verifiable AER-1 receipt attached: a public record of the job that anyone can open and re-check, without an account and without trusting the sender. The badge is a pointer to that practice, not a verdict on any single job. Whether one specific delivery checks out is answered only by that delivery's own receipt, which is why the honest pattern puts the badge and the job's receipt link side by side.
Does the badge mean Zambo verified my work?
No. The badge never means Zambo checked, approved, or endorses a specific job, and it must never be presented that way. A receipt proves the saved result was not changed since it was saved. It does not prove the work was correct. The only honest claim attached to a specific job is the one its own receipt supports when a reader checks it, and checking is free for anyone with the link.
Who can use the Verified with AER-1 badge?
Two groups. Implementations listed on the official AER-1 registry, which means they passed the conformance kit. And services whose deliveries carry AER-1 receipts, the way the worked example on this page does: the work goes out, and a receipt anyone can check goes out with it. If your work does not ship with receipts, the badge is not yours to use yet. Start by attaching receipts to your deliveries, then embed it.
How is this different from the per-receipt badge?
The per-receipt badge shows the live state of one receipt: this record, checked now, in one of its states. The Verified with AER-1 badge is about the sender, not a single record: it says this builder or service works in the open, with receipts attached as a matter of course. Use the per-receipt badge on a specific deliverable. Use this badge on your profile, your README, and your service page, and put the specific job's receipt link next to it wherever a specific job is being claimed.
Where does the badge have to link?
To this page, so any reader lands on the exact rules the badge operates under, or to the official AER-1 registry. A badge that links nowhere, or to a page that hides what it means, breaks the point of it: the claim and the means to check the claim travel together. Keep the link live. If you stop shipping receipts with your work, take the badge down.
Does the badge cost anything?
No. The badge is a static image and a link. Checking any receipt it points toward is free, for you and for your clients, with no account. The work of earning it is the receipts themselves: if your deliveries already carry them, embedding the badge takes a minute. If they do not, the free tier of the tools that mint receipts is where most senders start.
