How do I add AER-1 receipts to a LlamaIndex agent?
Install the aer1-llamaindex adapter, mint an AER-1 receipt at each query, retrieval, and tool step whose output you may need to defend, and verify the first receipts against the kit's conformance vectors. Retrieval steps matter most: their receipts are what let an answer be walked back to the sources it rested on.
LlamaIndex agents answer from retrieved material, which gives their receipts a distinctive job: not only proving a step ran, but binding the answer to the state of its sources. When a step's receipt commits to the saved output at execution (AER-1, IETF Internet-draft-zambo-aer1-21; kit version 1.5.4), and the surrounding record carries the source states, resolved, not resolved, or not checked, a later reader can separate the answer's grounded parts from its speculative ones without re-running anything.
Integration follows the same shape as the other framework quickstarts in this cluster: install the adapter, attach it where the agent is built, select the minting points (queries over client or regulated corpora, tool calls with side effects, delivered answers), and gate on the kit's conformance vectors before the wiring is trusted. Byte-level rules, member ordering for object inputs, label hygiene, are the draft's, and the vectors exist to prove your build obeys them.
The use case that usually justifies the work is the audit question: a client, a reviewer, or your own future self asks what an answer was based on. With receipts at the retrieval steps, that question has a documentary answer. Without them, it has a re-run, which produces a new answer rather than evidence about the old one.
Quickstart: AER-1 receipts for LlamaIndex agents
1. Install: pip install aer1-llamaindex. 2. Attach the adapter at agent construction. 3. Select minting points: retrieval and query steps over material that matters, tool calls with side effects, delivered answers. 4. Run one question whose sources you can inspect by hand. 5. Verify: conformance vectors pass; the answer's steps walk back to their sources on the record; one receipt checks at https://zambo.dev/verify/ . 6. Runbook entry: package version, kit 1.5.4, minting-point rule.
Worked example
The verification anchor is the kit fixture receipt 130da435-e157-498e-af90-605866a86a27, the fixed point every conforming implementation reproduces. A LlamaIndex integration that passes the vector suite is making receipts the same way the independent implementations do, which is the property your future checker relies on.
Frequently asked questions
Do receipts record the retrieved documents themselves?
The receipt commits to the step's saved output; the record around it carries the source states. Design your steps so the saved output names the sources used, and the walk-back works without storing whole corpora in receipts.
We already log our queries. What do receipts add?
Independent recompute. A log is your system's account; a receipt can be checked by a third party against a published format, which is the difference when the answer is disputed by someone who does not run your stack.
Should indexing steps mint receipts too?
Index builds change what future answers can say, so yes for production corpora: an index step receipt dates the corpus state every later answer silently depends on.
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