How do I get a receipt for work done in Gemini?
Add the Zambo connection to Gemini, then run the work through it. Each step is saved as a verifiable receipt at the moment it runs, with its result and source states, and the job closes into a handover link your client can check in a browser. The chat stays a chat; the record is separate.
Gemini on its own gives you a conversation. A conversation is a fine working surface and a poor receipt: it mixes drafts with deliveries, it cannot be recomputed by anyone else, and it ends where the session ends. The receipt comes from the layer the work runs through, not from the model that did the thinking.
The setup is the standard one for supported clients: add https://zambo.dev/mcp as a connection (the /add/ page carries the per-client screens), then start the job in the connected session. Steps taken through the connection's tools are saved as AER-1 receipts (IETF Internet-draft-zambo-aer1-21) as they execute. Research steps show their source states; production steps show their saved results; the whole job reads at /today and delivers as a handover.
The boundary, stated before you rely on it: a Gemini chat that never touches the connection leaves no receipt, and no tool can mint one afterwards. Route the client work through the connection from the first step, and keep pure brainstorming unrecorded if you prefer; the record's gaps will honestly show which is which.
Checklist: your first Gemini receipt
1. Add the Zambo connection to Gemini from the /add/ page. 2. Open a new session and state a small, real task. 3. Let the work run through the connection's tools. 4. Open the job at /today and read its steps in order. 5. Check one receipt at https://zambo.dev/verify/ . 6. Build the handover and send the link with the delivery.
Worked example
Sample: a marketer asks Gemini to research five competitors and draft a comparison brief. Through the connection, the research steps save their source states (four resolved, one not resolved) and the drafting step saves its result. The client receives the handover, sees the brief, and sees the one source that never resolved, labelled, instead of discovering it in a dispute. (Sample scenario; no live record is cited.)
Frequently asked questions
Does Gemini itself issue the receipt?
The receipt is issued by the connection the work runs through, in the AER-1 format, and it records the step's saved result regardless of which supported client drove it. Gemini does the work; Zambo keeps the record.
Can I get a receipt for a Gemini chat from last week?
No. Receipts are saved at execution time for work run through the connection. Last week's chat can be summarized into a new, clearly labelled job, but its steps were not recorded when they ran.
Will the client see that Gemini did the work?
The step records carry the producer label recorded at the time, so yes, where the record says so. Clients consistently prefer the labelled record to an unlabelled claim.
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