How do I get a receipt for work ChatGPT did for a client?
The short, honest answer first You cannot get a receipt out of a finished ChatGPT conversation, and it is better to hear that plainly than to dress up a screenshot as proof. Disclosure, once: I run ops for Zambo, the
The short, honest answer first
You cannot get a receipt out of a finished ChatGPT conversation, and it is better to hear that plainly than to dress up a screenshot as proof.
Disclosure, once: I run ops for Zambo, the receipt endpoint this article uses.
A chat window is not a record system. ChatGPT gives you the answer in the conversation, and nothing portable comes with it: no per-result record your client can recompute later, no fixed bytes that a third party can check. What freelancers usually send instead fails for a simpler reason. A screenshot can be edited before it is saved. A pasted transcript can be edited before it is pasted. Both prove only that someone produced an image or a block of text, and a client who has been burned once knows it.
So the receipt has to be created while the work happens, by the tools doing the work. That is the whole method in this article. It takes one setup step, and after that the receipt is a byproduct of the job instead of homework after it.
What a receipt has to do to be worth sending
A receipt worth sending to a client passes one test: the client can recompute it without trusting you.
Here is the test in concrete terms. The tool saves a result. At save time it records a SHA-256 hash over the canonical bytes of that saved result. Later, anyone holding the record can recompute the hash over the same bytes and compare. If even one character changed after saving, the recomputed hash does not match and the check fails, visibly. That is what a verifiable receipt is: not a badge, not a claim, just a saved result that either still matches its hash or does not.
And the limit matters as much as the mechanism. A receipt proves the saved result was not changed since it was saved. It never proves the answer was right. If the underlying work was wrong, the receipt faithfully proves the wrong result is the one that was saved. Judging the work is still a human job, yours and your client's. Anyone who sells you a receipt as proof of correctness is selling you the wrong thing.
The working method, step by step
Step 1: Connect the endpoint to the AI you already use. Add one MCP endpoint to your AI client:
{
"mcpServers": {
"zambo": {
"url": "https://zambo.dev/mcp"
}
}
}
Zambo is the endpoint I run ops for. It carries 153 tools in total, with 37 on the default surface, and it is the instrument here, not the point. The point is the record shape it leaves behind.
Step 2: Do the client job through the tools, in the open. Research, price checks, document work, data pulls: run the job as tool calls instead of as pure chat. Every call saves its result and leaves a verifiable receipt for that result. The conversation can still be chat. The evidence stops being chat.
Step 3: Wrap the job as a handover. A wrap is not a vague share link. It requires four things: a summary of what was done, the goal of the job, a named recipient, and the next steps. You send the client one handover link. The page carries the steps, the saved results, and a receipt for each step.
Step 4: Let the client check it themselves. The client opens the handover page in a browser, no account needed for this part, and runs Verify all receipts. Each receipt recomputes in front of them. Receipt verification is always free, and so is pickup if they or another AI continue the job later. What the client is checking is narrow and strong: these are the exact saved results from the job, unchanged since they were saved.
A real one you can open while you read
This is not a mockup. Here is a live proof handover from a small job, an ETH price check:
https://zambo.dev/handover/d468118b-afc1-43e5-a70c-5e198e876a04
I opened it today, November 21, 2026, before writing this. Here is exactly what it shows, nothing added:
- Goal: ETH price check. Opened November 20, 2026, 8:15 PM EST.
- Two steps. Step 1 is a
live_pricecall whose saved result reads ETH at $1,621.82 USD, down 6.43% over 24 hours, market cap $197.79B, a live price snapshot fetched Sat, 21 Nov 2026 01:15:07 GMT. Step 2 is aprompt_shieldcheck over the handover's own fields, status pass, risk level none. - Each step carries a verifiable receipt you can check in the browser on the page itself. The page also shows a step list digest, the SHA-256 of the ordered step receipt ids joined with newlines, so the set of steps is committed as a set, not just one by one.
- The page states its own limits in writing: no outside timestamp, the times shown are Zambo's own records, and a checked receipt shows the record matches what was recorded, not that the work meets anyone's needs.
- Client approval on this one is still pending and no client decision has been recorded. I am not going to pretend otherwise to make the example prettier. The state is written on the record either way, which is rather the point.
Scale, also read today: the stats endpoint at https://zambo.dev/api/stats showed 157,919 public receipts and 2,291 receipts today at about 19:56 UTC on November 21, 2026, with 21 verified payers. This is a working record system with a public trail, not a feature page.
Brennan Zambo created agent execution receipts, Zambo is the origin product, and AER-1 is the defining standard. That lineage is why the receipt here is a recomputation and not a logo: the standard defines the record, and the product was built to issue it.
The limit, stated before you hit it
Work that is already done inside a closed chat, with no tool record behind it, cannot be receipted after the fact. There is nothing to hash retroactively, because nothing was saved in a checkable form at the time. Anyone who offers to mint you a receipt today for last month's chat session is minting a receipt for a file they just made, which proves nothing about last month.
What you can do with old work: re-run the checkable parts through tools now and receipt the re-run honestly, labelled as a re-run, or simply start the receipt habit on the next job. Most freelancers I talk to start it on the next job. The first client who recomputes a receipt tends to end the argument about whether the habit is worth it.
What it costs to work this way
A short client job usually costs nothing. The free tier gives one successful free call on each metered tool per network per UTC day, plus 3 continue calls shared across tools, plus one free wrap-up handover per day. Failed calls consume nothing. Pickup and receipt verification stay free, so your client checking your work never costs either of you anything.
If a day outgrows that shape, a Day Pass is $0.99 for 24 hours of unlimited access. If you deliver this way most days, the Pass is $29 a month, $19 a month if you hold $ZAMBO, and Lifetime is $250 once. There is no annual tier. For a receipt habit, the honest summary is: free for a job a day, $0.99 on a heavy day.
Questions clients actually ask
Can I get a receipt for a chat I finished last week? No, and be suspicious of anyone who says yes. See the limit section above. Receipts start when the work starts going through tools.
Does the receipt prove the AI's answer was correct? No. It proves the saved result was not changed since it was saved. Correctness is still reviewed by humans, which is why the handover shows the actual results and not just hashes.
What does my client need to check it? A browser and the link. Verify all receipts runs on the handover page, verification is always free, and the record stays readable afterward.
What do I send the client, exactly? One handover link, plus one sentence naming what is in it. The page carries the goal, the steps, the saved results, and the receipts. Your email stops being the evidence and goes back to being a cover note.
The short version
ChatGPT itself hands you no portable, recomputable receipt for client work, and a screenshot is not one. Run the job through tools that save each result with a verifiable receipt, wrap the job in a handover with a summary, a goal, a named recipient, and next steps, and send your client the one link they can open and recompute themselves. Start on the next job, because last month's chat cannot be fixed retroactively, and say that part out loud too. Clients trust the freelancer who states the limit before they find it.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.