How do I get a receipt for work done in Claude?
Add the Zambo connector: https://zambo.dev/mcp . Then run the work through the connector in Claude. Each step is saved as a verifiable receipt as it runs, with its result and source states, and the job closes into a handover link your client can check in a browser, no Claude account needed.
Claude's conversations are excellent working surfaces and poor archives: drafts, reasoning, and results scroll together, and none of it can be recomputed by the client who paid for the outcome. The receipt comes from the connector the work runs through, which is why the add is the whole setup: one connector, added once, in Claude's own settings.
From then on, work Claude drives through the connector's tools is recorded step by step (AER-1 receipts, IETF Internet-draft-zambo-aer1-21). Research steps show what they rested on, with sources resolved, not resolved, or not checked. Production steps save their results. The job reads at /today as it grows, and delivers as a handover when it closes.
The standing boundary applies with full force to Claude's long, capable sessions: thinking and drafting that never touch the connector leave no receipts. Make the connected session the default for client work, and keep the unconnected one for exploration. The record's step labels will show which was which, honestly, which clients read as professionalism.
Checklist: your first Claude receipt
1. Add the Zambo connector: https://zambo.dev/mcp (the /add/ page shows the current Claude screens). 2. Start a connected session and assign a small, real task. 3. Let the steps run through the connector's tools. 4. Read the job at /today; note the source states. 5. Check one receipt at https://zambo.dev/verify/ . 6. Deliver with the handover link.
Worked example
Sample: a consultant asks Claude to research a market question and draft a briefing. Through the connector, the research steps save their sources (five resolved, one not resolved and flagged), and the drafting step saves its output. The client receives the handover and reads the brief and the flagged source in the same sitting. (Sample scenario; no live record is cited.)
Frequently asked questions
Does Claude issue the receipt itself?
The receipt is issued by the Zambo connection the work runs through, in the AER-1 format. Claude does the work; the connection keeps the record, which is why the same record format works across every supported client.
Can I get receipts for an existing Claude conversation?
No. Receipts are saved at execution for connected work. An existing conversation can be summarised into a new, labelled job, but its original steps were not recorded when they ran.
Will my client need Claude to check the receipt?
No. The handover opens in any browser and the receipt recomputes at the public verify page. The check belongs to the record, not to the tool that produced the work.
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