ZAMBO.

How do I get a receipt for work done in Claude?

Claude can think hard and still hand you a summary you cannot check. The fix is not another summary, it is a record: route the real work through tools that receipt themselves, and every call leaves a saved receipt anyone can open. Adding the connection takes a few minutes once. Here is how it works, in Claude, end to end.

See it live: generate a real verifiable receipt in 30 seconds, no signup.

Run your first job now, no signup

Fastest path: open zambo.dev/chat and ask for a live BTC price. It runs a real tool call and hands you a verifiable receipt, no account, no install.

In Claude Code, one line adds the endpoint:

claude mcp add --transport http zambo https://zambo.dev/mcp

Then ask your agent: "What is the live BTC price?" The answer comes back with a receipt link. Cursor and VS Code take the same URL in their MCP settings.

Claude, connected in seven steps

  1. Open the connectors or MCP settings in Claude (desktop or web).
  2. Add a custom connector.
  3. Paste https://zambo.dev/mcp as the server URL. No API key needed; leave the key field alone.
  4. Save the connector.
  5. Start a fresh chat, so the session picks up the current connector list.
  6. Confirm the tools appear.
  7. Run a small test call you can check the answer to, for example a live price.

From that chat on, when Claude calls a Zambo tool, the result comes back with a receipt link. That link is the receipt for the work: the tool that ran, the UTC time, the saved result, and a SHA-256 commitment anyone can recompute.

A live example

Asked through the endpoint on 23 October 2026, live_price answered: BTC $81,632.00 USD, up 0.21% over 24 hours, market cap $1640.85B, via CoinGecko at 2026-10-23T16:36:58 UTC. The call's public receipt is zambo.dev/run/ccb2ac0f-2998-49fe-9cc1-d766f789e028. Open it and check the fingerprint at zambo.dev/verify. A match proves the saved result was not changed since it was saved. It does not prove the price was right, and no receipt can.

What counts as "work done in Claude" for receipts

Receipts cover tool calls made through the connection: live checks, audits, extractions, data lookups, saves, handovers. When your job can be done with tools, route it that way: ask Claude to check the price, audit the page, read the PDF, save the result. Each step receipts itself, and the day's calls line up in order in the connection's Today view, so a client or a manager can follow the whole job, not just the final paragraph.

The honest boundary: native chat work

Work Claude does purely in conversation, writing text with no tool call, has no tool to receipt. The remedy used by the people who need the record is to package the session into a handover: one link carrying the goal, the steps, the outputs, and open items, which the receiver can accept or flag. Handover is for the chat-shaped work; receipts are for the tool calls. Together they cover the job.

Costs, in one paragraph

Starting is free and needs no Zambo account: the free tier gives you 20 free calls per day. A $0.99 Day Pass for 24 hours lifts the metered limits for one heavy day. The Zambo Pass is $29 for 30 days, one payment, at the same endpoint, with a receipt on every call. People pay by PayPal or card through PayPal; agents pay in USDC on Base via x402.

Questions, answered

How do I get a receipt for work done in Claude?

Add the Zambo MCP connector to Claude once (custom connector, URL https://zambo.dev/mcp, no API key, fresh chat). After that, every Zambo tool call Claude makes returns a verifiable receipt at a public /run/ link: the tool, the UTC time, and the saved result, with a SHA-256 commitment anyone can recompute at zambo.dev/verify.

How do I get a receipt for work done in Gemini or Grok?

The same way. Zambo is one remote endpoint and every MCP client takes the same URL, https://zambo.dev/mcp. Add it in the client's connector or MCP settings, start a fresh session, and tool calls leave the same receipts with the same check.

Can I get a receipt for a Claude chat that used no tools?

Tool receipts cover tool calls. For pure chat work, package the session into a handover: one link with the goal, steps, outputs, and open items, which a receiver can accept or flag. The two records together cover the whole job.

Proof works best when it travels with the work itself. The AER-1 badge kit turns verifiable receipts into an embeddable badge for project pages, docs, and profiles, so anyone who sees the claim can reach the check in one click.

The short version on the main site: how do I get a receipt for work done in Claude?

Related

Read the AER-1 IETF Internet-Draft. Browse the public registry of AER-1 implementations.

See it on a real call: the live demo runs one real Zambo call and hands you its verifiable receipt, no signup. To put a receipt under every call your agent makes, a Zambo Day Pass unlocks everything for 24 hours for $0.99.