How do I get a receipt for work done in Grok?
Connect Grok to the Zambo connection, and run the work through it. Each step is saved as a verifiable receipt (AER-1) as it executes, with the saved result and the source states, and the finished job becomes a handover your client can open and check without any account.
Grok's strength is speed of thought; its weakness, shared with every chat surface, is that the session is the only artifact. When a client asks what the work was based on, a scrolled conversation is a claim. The receipt moves the evidence out of the session and into a record designed to be checked by someone who was not there.
The mechanism is the same as for every supported client: one connection, https://zambo.dev/mcp , added once (the /add/ page shows the current screens for each client). Work the agent performs through the connection is saved step by step. Research steps carry their source states, so a claim in the output can be walked back to what was resolved, what was not resolved, and what was never checked. Delivery is the handover link, and the Receipt Bot's nightly habit, collecting and filing receipts for bot work, starts from the same records.
The limit is the standing one, and it matters more with fast tools: only work run through the connection is recorded. A brilliant Grok answer produced in a bare chat leaves no receipt, and none can be created later. Make the connection the default for client work and the record builds itself.
Checklist: your first Grok receipt
1. Add the Zambo connection to Grok from the /add/ page. 2. Start a session and assign a real, small task. 3. Let the steps run through the connection's tools. 4. Read the job's steps at /today; note the source states. 5. Check one receipt at https://zambo.dev/verify/ . 6. Deliver with the handover link, not a screenshot of the chat.
Worked example
Sample: an operator asks Grok to scan overnight agent activity and summarize exceptions. Through the connection, the scan steps save their results, two flagged jobs show their own receipts, and the summary step saves its output. The morning reader opens one record instead of three chats, and every claim in the summary has a step behind it. (Sample scenario; no live record is cited.)
Frequently asked questions
Does the receipt cover Grok's own posts or actions outside the connection?
No. The receipt covers steps run through the Zambo connection. Actions Grok takes anywhere else are outside the record, and the record will not pretend otherwise; route the work you need to prove through the connection.
Can my client check a Grok receipt without a Grok account?
Yes. The check is a property of the receipt, not of the client that produced it. The handover opens in a browser and each receipt recomputes at the verify page, no Grok account involved.
Is setup different for Grok than for other clients?
The pattern is identical: one hosted connection, added in the client's own settings, a minute of work. Only the screens differ, and the /add/ page keeps the current per-client steps.
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