Direct answer
Gemini keeps the chat. A receipt keeps the proof.
Work done in Gemini leaves you a conversation. Months later, when a client asks what was actually produced, or a teammate has to continue the job, the conversation is the weakest evidence in the building: it lives in one account, it scrolls the thinking and the result into one thread, and any copy of it could have been edited before it reached the reader. A receipt is the missing object. It is issued per job while the work runs, it holds the steps and the saved outputs, and it can be rechecked by a person who has no Gemini account and never saw the chat. Gemini does not issue it. The work has to run through a layer that does, and this page is that setup, start to finish.
Updated November 2, 2026. First published November 2, 2026.
Step 1. Know what the receipt has to survive
The test of any proof is the moment it gets used. A client disputes what was delivered. A manager asks what the team produced this month. You move the project to a different AI and need the new one to trust the record of the old one. In each moment, the person reading the proof was not present when the work ran, and they know a chat export came from the person it defends. The receipt survives those moments because of how it is made: created by the executing system at run time, in the AER-1 format published as IETF Internet-Draft draft-zambo-aer1-26, and checkable at https://zambo.dev/verify/ by anyone holding the link. It proves the saved result was not changed since it was saved. Judging whether the result was right remains a human act, and the receipt never claims otherwise.
Step 2. Connect the endpoint to your Gemini client
The connection is one MCP endpoint: https://zambo.dev/mcp. Add it to the Gemini client you work in, and the jobs you route there run against 153 tools, 36 of them on the default surface, with a verifiable receipt returned on every call. No API key, no signup. The free tier is 20 calls + 1 wrap-up free every day; picking up in another AI is always free. Keep the division clean: conversation and drafting can stay in the chat, and the jobs you may one day need to answer for (research with sources, audits, deliverable builds, checks) run through the endpoint so the record exists from the first step.
Step 3. Send the link, and let the reader run the check
Every receipt lives at its own address, https://zambo.dev/run/ followed by the receipt ID. Send that link with the deliverable. The reader opens the job record, sees the steps and the saved outputs, and sees the check state. If they want the check without the issuing service in the middle, the format is public: the conformance corpus at https://zambo.dev/aer1/corpus.json publishes 126 vectors and 129 checks for the AER-1 format, and independent implementations evaluate records against it. A proof that only the issuer can check is a claim. A proof any checker can run is a receipt. File the link with the job, in the ticket or the delivery note, so the record is findable on the day it is needed rather than reconstructed from a chat history under pressure.
Step 4. Wrap up so the job can leave Gemini intact
Gemini is rarely the last tool a job touches. The wrap-up call seals the session into a handover: one record carrying the steps, the outputs, the receipts, and the state of any decision. Send that link to the next AI, the teammate, or the client. The receiving AI picks the work up from the record and continues it, and picking up in another AI is always free, so continuity never waits on a payment. If the client must accept the delivery, the acceptance is recorded on the handover itself. What arrives on the other side is not a summary someone wrote about the work. It is the work, with its evidence attached.
What a record does not settle
A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the result was correct, it does not resurrect chats or jobs that ran unrecorded, and it cannot be issued after the fact for earlier Gemini sessions. This page is general information, not legal advice.
Frequently asked questions
How do I get a receipt for work done in Gemini?
Connect the Zambo MCP endpoint, https://zambo.dev/mcp, to the Gemini client you work in and run the job through the endpoint. Each call returns a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, with a link in the form zambo.dev/run/ followed by the receipt ID. The receipt records the steps and the saved outputs of that job, and anyone can recheck it at https://zambo.dev/verify/ without a Gemini account and without seeing your chats. The receipt exists because the endpoint issued it while the work ran, not because the chat was saved.
Why is the Gemini chat itself not a receipt?
A chat is a transcript you hold, and a transcript can be copied, trimmed, reordered, or deleted, by you or by the passage of time and a closed account. It also mixes the asking, the wandering, and the answer into one scroll, so a reader cannot tell which output was the delivered result. A receipt is narrower and stronger: one job, its steps, its saved outputs, and a check that recomputes whether that saved result still matches the record. When someone questions the work months later, the chat asks them to trust your copy. The receipt lets them run the check themselves.
Can the work move to another AI and keep its receipts?
Yes. End the Gemini session with the wrap-up call and the work seals into a handover record: the steps, the outputs, and the receipts in one link. The receiving AI picks the handover up and continues from the record instead of from a pasted summary, and picking up in another AI is always free. The receipts issued along the way stay attached to the record, so the history of the job crosses the switch with the work itself. That is the difference between moving a conversation and moving a job: the conversation restarts the argument about what happened, the record settles it.
Can I get receipts for Gemini work I did last month?
Not for those runs. Receipts are issued at execution time, and a chat kept afterwards cannot be turned into one honestly. What you can do now is rerun the checkable parts of that work through the endpoint: the audit, the comparison, the summary of what was delivered. Those runs issue receipts dated today that record what the checks found today. Present them as a dated verification of the earlier work, and start the receipt habit with the next job, where the record will cover the work from its first step.
What does it cost to add receipts to my Gemini work?
The free tier is 20 calls + 1 wrap-up free every day; picking up in another AI is always free, and there is no API key or signup to start. For $0.99, a Day Pass makes the endpoint unlimited for 24 hours, no subscription: get the Day Pass. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.