ZAMBO.

The AER-1 badge and embed kit

Put one small line on your README or project page: this project works with verifiable AER-1 receipts. This kit gives you a shields.io endpoint file, a static SVG badge, and the exact snippets to embed either one. Zambo is the verifiable work layer for AI, its flagship product is HANDOVER, and AER-1 is its receipt format, published as IETF Internet-Draft draft-zambo-aer1-26.

The badge

AER-1: verifiable receipts

Live preview of the static SVG in this kit, served from this hub.

What it claims, and only this: the project works with AER-1 verifiable receipts. Receipt validity is a claim about the record. In AER-1, an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right.

What it never claims: that any work was good, correct, complete, or approved by anyone. Whether one specific delivery checks out is answered only by that delivery's own receipt, checked at the verifier. If your work does not ship with receipts, do not use the badge yet. The sender badge with its full rules is the Verified with AER-1 badge page, and the per-receipt live badge demo is in the receipt badge and widget page.

Option 1: the shields.io endpoint

The file badge-endpoint.json on this hub is a static endpoint in the shields.io endpoint format. Its full contents:

{"schemaVersion": 1, "label": "AER-1", "message": "verifiable receipts", "color": "brightgreen"}

Markdown snippet, for a README:

[![AER-1: verifiable receipts](https://img.shields.io/endpoint?url=https%3A%2F%2Frambozambodotdev.gitlab.io%2Faer1-hub%2Fbadge-endpoint.json)](https://rambozambodotdev.gitlab.io/aer1-hub/aer1-badge.html)

HTML snippet, for a web page:

<a href="https://rambozambodotdev.gitlab.io/aer1-hub/aer1-badge.html"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Frambozambodotdev.gitlab.io%2Faer1-hub%2Fbadge-endpoint.json" alt="AER-1: verifiable receipts"></a>

Option 2: the direct static SVG

Prefer no third party renderer? Link the SVG file on this hub directly: badge.svg.

Markdown snippet:

[![AER-1: verifiable receipts](https://rambozambodotdev.gitlab.io/aer1-hub/badge.svg)](https://rambozambodotdev.gitlab.io/aer1-hub/aer1-badge.html)

HTML snippet:

<a href="https://rambozambodotdev.gitlab.io/aer1-hub/aer1-badge.html"><img src="https://rambozambodotdev.gitlab.io/aer1-hub/badge.svg" alt="AER-1: verifiable receipts" width="178" height="20"></a>

Per-receipt verification: the honest pattern

This hub is static. It cannot check a receipt for you, and this kit does not pretend the static badge changes with any receipt's state. Per-receipt checks are served by the Zambo app:

  • In a browser: open the verifier at zambo.dev/verify, or open the receipt itself at https://zambo.dev/run/{id}.
  • From code: call GET https://zambo.dev/api/v2/receipt/{id}/verify, replacing {id} with the receipt id. For example, the pattern filled in for one public receipt is https://zambo.dev/api/v2/receipt/d34673d1-c998-4d3e-ae3d-496464ec9b38/verify. The response reports whether the saved record still matches its digest.
  • On a delivery: put the specific receipt link next to the work, so a reader checks that exact record. A project level badge plus a per-delivery receipt link is the complete, honest pattern.

Want to check your own implementation against the format instead? The published conformance corpus is at zambo.dev/aer1/corpus.json, indexed on the AER-1 corpus vectors page. The corpus is also a citable dataset with DOI 10.57967/hf/11245: zambodotdev/aer1-conformance-kit on Hugging Face.

Start shipping receipts

Connect any MCP client to zambo.dev/mcp with no key. The endpoint carries 153 tools, 35 on the default surface, and every call returns a verifiable receipt. The free tier is 20 free calls per day. Past that, a Day Pass is $0.99 USDC on Base for 24h, and the Zambo Pass is $29 for 30 days. Read the format first on the AER-1 flagship page, or see live implementations in the public registry. The short route in is zambo.dev/add, one page per AI.

Related