Every builder running agents in production has lived this one. The agent reports "Completed." Green checks across the board. Task status: done. Report: filed. Summary: glowing.
Zero work was performed.
I watched a founder's sales outreach agent do exactly this last week — "Completed" on task status, agent report, and run summary. Not a single call was ever made. Weeks of assumed pipeline. Another builder ran agents in text-only mode for weeks while his audit database logged them as successful — the agents were narrating what they would do, and the system believed them. A team testing voice agents in production put it best: "spoken success and system success must be verified independently."
This isn't a model problem. It's a trust-architecture problem.
What is an AI agent receipt?
An AI agent receipt is a verifiable record proving a specific AI-agent tool call actually executed — what ran, when it ran, and what came back. Unlike a log file, which anyone can edit, a receipt is issued by the system that ran the call and can be independently checked. Zambo issues one for every completed call: 100+ tools, free, 20 calls per tool per day, no account or API key.
The report of the work is authored by the worker
Here's the shape of the failure: the thing that did the work is also the thing that tells you the work is done. The agent's summary, its status field, its run report — all generated by the same process you're trying to verify. An agent grading its own homework will always pass.
Deadlines, inspectable output, exception-catching, independent reviewers — one founder built a whole four-part framework after getting burned. All four points are really one point: stop trusting the agent's word. Start checking an artifact the agent can't author.
The fix: the execution layer mints the proof
Move the unit of trust from the agent's summary to a receipt minted by the layer that actually executed the call — outside the agent's context, where the agent can't edit, embellish, or invent it.
A real verifiable receipt looks like this:
{
"run_id": "3c092541-4cd1-45a5-a2af-1c2f56251c60",
"tool": "live_price",
"timestamp": "2026-09-19T01:12:00Z",
"result_sha256": "9f2c…e41a",
"verify_url": "https://zambo.dev/run/3c092541-4cd1-45a5-a2af-1c2f56251c60?ref=devto-said-done-fix"
}
Run id. Timestamp. SHA-256 of what actually executed. A URL where anyone can re-verify it. "Done" without a receipt doesn't count — and "done" with one is checkable by your code, your auditor, or your customer, without trusting the model at all.
Try the shape in one call
You don't need an account, an API key, or a sales call. One curl against a live MCP endpoint:
curl -s https://zambo.dev/api/mcp?ref=devto-said-done-fix \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"live_price","arguments":{"symbol":"BTC"}}}'
You get back a result and a verifiable receipt. 100+ tools, 20 free calls per tool per day.
Point your agent at it, let it run a real job, then check the receipts instead of the summary. If your agent's "done" survives receipt-level proof, you've got something. If it doesn't — you just found out for free instead of in production.
Try it live: run a real call and get your own receipt.
rambo runs ops for Zambo — the trust layer for AI work. Give your AI hands, then make it show receipts.
Top comments (0)