What a zambo receipt is
an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right.
That last clause matters. A receipt does not grade the work. It fixes the record, so the work can be judged against what was actually saved at the time, not against a summary written later. Zambo, the verifiable work layer for AI, files one of these records for every call run through its endpoint, in the open AER-1 format published as IETF Internet-Draft draft-zambo-aer1-26.
How to check one: open the receipt link to read the tool, the input, and the saved result. Then paste the receipt id into zambo.dev/verify, or call the public verify endpoint, and the digest over the saved bytes is recomputed and compared with the digest filed when the call ran. A match means the saved result is the result that was saved. No account is needed.
The curated set: eight real jobs, eight checkable records
These receipts come from the public stream at zambo.dev/api/receipts/recent. Each row links to the live run page for that call, where the full record sits in the open.
| Job | Tool | What the receipt records | When (UTC) |
|---|---|---|---|
| Open the receipt | handover | One agent handed a job to the next agent, with the state of the work attached so the work could continue without starting over. | 2026-10-23 00:25 |
| Open the receipt | workflow_close | A two-step workflow was closed into one snapshot record, so the whole job can be read back at once instead of call by call. | 2026-10-23 00:11 |
| Open the receipt | memory_remember | An agent saved a fact to shared memory, so a later session, or a different AI, can pick it up instead of asking again. | 2026-10-23 00:03 |
| Open the receipt | continuity_get_recent | An agent pulled its recent session history to resume work where a previous session left off. | 2026-10-23 00:36 |
| Open the receipt | live_price | An agent fetched a live bitcoin price at the moment of the call, instead of answering from training data. | 2026-10-23 00:25 |
| Open the receipt | prompt_shield | A prompt that tried to override the agent instructions was screened and flagged as a jailbreak attempt, and that screening result is the saved record. | 2026-10-23 00:36 |
| Open the receipt | ghost_audit_site | A website audit of zambo.dev was launched, and the launch record, with its report links, was saved for anyone to re-read later. | 2026-10-23 00:33 |
| Open the receipt | capability_search | An agent searched the capability catalog for the right tools for a research job before starting, and the search itself left a receipt. | 2026-10-23 00:35 |
Want the unfiltered view instead? The receipt stream counts the whole public flow, day by day and tool by tool.
Add Zambo free, in the client you already use
Checking receipts is free forever, with no account. Producing them is free to start: 20 free calls per day, then upgrade only if the work earns it. One connection covers every surface below, because they all point at the same endpoint, https://zambo.dev/mcp. The guided page for every client is zambo.dev/add.
Claude
In Claude, open the connectors or MCP settings, add a custom connector, and paste https://zambo.dev/mcp as the server URL. No API key. Start a fresh chat, run one small call, and open its receipt to confirm the path works end to end. Step by step: add Zambo to Claude.
ChatGPT
In ChatGPT, add a custom MCP server in settings and paste https://zambo.dev/mcp as the server URL. No API key. Start a new chat and run a first checked call. Step by step: add Zambo to ChatGPT.
Cursor
Add the config below to .cursor/mcp.json in your project, or to the global Cursor MCP config, then restart Cursor and the Zambo tools appear in the agent tool list. Step by step: add Zambo to Cursor.
Grok
Where your Grok setup accepts an MCP server, add https://zambo.dev/mcp, one URL and no key, then start a new session and confirm the tools are listed. For bot work, the Zambo Receipt Bot on x.ai files receipts for bot jobs. Step by step: add Zambo to Grok.
Any MCP client: the generic config
Most MCP clients take the same snippet. Paste it into the client config, restart the client, and run one call:
{
"mcpServers": {
"zambo": {
"url": "https://zambo.dev/mcp"
}
}
}
Then check the receipt your first call returns, free, at zambo.dev/verify. When one job becomes every job, a Day Pass covers 24 hours of full access for $0.99, and ongoing use is the Zambo Pass at $29 per month or $290 per year.
Your first call: search for your own job, under your label
Do not take the tour. Make the first call a catalog search for the problem you actually have, and pin a caller label and a session id on it. Every Zambo tool accepts both as call arguments; reuse the same pair on every call and your usage is counted under one identity, with your limits and any pass attached to that label:
{
"tool": "capability_search",
"arguments": {
"q": "the job you need done, in your own words",
"_caller_label": "your-fleet-or-project-name",
"_session_id": "your-stable-session-name"
}
}
In Zambo's own receipt stream, callers whose first call is a catalog search for their specific job come back on a later day at 42 percent, against a 25 percent baseline for everyone else. Labeled callers carrying stored state are the ones who build the longest records on the stream.
Keep going
- Run an AI agent fleet on one Zambo: one identity, one notebook, one receipt stream.
- The receipt stream: the whole public flow, counted daily.
- Check any agent's work: the checking skill, for work an agent did while you were away.
- AER-1: the open receipt standard behind every receipt on this page, draft-zambo-aer1-26.
- Workflow close receipts: how a whole job, not just one call, gets one checkable record.
- zambo.dev/add: connect your AI once, and every job after that carries a receipt.