How do I get a receipt for work ChatGPT did for a client?
Add the Zambo connection to ChatGPT, then run the client work through it. Steps are saved as verifiable receipts as they execute, and the finished job becomes a handover link: the client opens it, reads the steps and their sources, and records their acceptance, all without a ChatGPT account.
ChatGPT is where a large share of client-facing AI work happens, and its native artefact, the shared chat link, proves a conversation occurred. It does not prove the work in the checkable sense: the conversation can scroll past drafts and dead ends, its contents sit inside one platform's presentation, and no step in it can be recomputed by the client.
The connection pattern repairs that, as it does for every supported client: add https://zambo.dev/mcp once (the /add/ page carries the current ChatGPT steps), then start client jobs in the connected mode. Steps taken through the connection save their results as AER-1 receipts (IETF Internet-draft-zambo-aer1-21) at execution time, research steps carry their source states, and the job delivers as a handover built for the client's reading, not the operator's.
Keep the boundary explicit with clients and with yourself: chats outside the connection are unrecorded, and that is fine for exploration. Client work starts connected, so its record exists before the invoice does. The record's producer labels also settle the recurring ChatGPT question, what did the AI do versus what did you do, by showing both kinds of step on one job.
Checklist: your first ChatGPT client receipt
1. Add the Zambo connection in ChatGPT from the /add/ page. 2. Open a connected session for the client job. 3. Run the work through the connection's tools from the first step. 4. Read the steps at /today; check the source states. 5. Verify one receipt at https://zambo.dev/verify/ . 6. Send the handover link as the delivery and take the client's decision on it.
Worked example
Sample: a copywriter produces a landing page draft for a client in ChatGPT. Through the connection, the research step saves three resolved competitor sources, the draft step saves its text, and the copywriter's revision is a labelled step of its own. The client approves on the handover, seeing the whole path. (Sample scenario; no live record is cited.)
Frequently asked questions
Is a shared ChatGPT link not enough proof?
It proves a conversation happened and shows its contents as the platform presents them. It does not fix any step's result at execution, cannot be recomputed by the client, and records no acceptance. For friendly transparency it is fine; for proof it is the weak form.
Can the client check the work without paying for anything?
Yes. Checking is free and accountless: the handover in a browser, receipts at the public verify page. Payment exists on the producing side, where the work and the record are made.
Does the setup work for team ChatGPT workspaces?
The pattern is per-connection: each workspace user who produces client work adds the connection, and jobs carry their producer labels, so a team's records stay attributable person by person.
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