ZAMBO.

How long does it take to set up receipts for an AI agent? One paste, then the first call.

The short answer: minutes, and most of them are spent finding the settings screen in the client you already use. The whole setup is adding https://zambo.dev/mcp as a remote MCP server, exactly as the add Zambo to your AI page walks through per client. There is no API key, no account, and nothing to install server-side. The first receipt is not a second step: it arrives with the result of the first call, because the record is created when the call executes.

Time the round trip yourself: the live demo runs one real call and hands you its verifiable receipt in about 10 seconds, no signup. Setup puts that same round trip inside your own agent.

Published October 25, 2026. Steps and prices checked against zambo.dev/add and the live endpoint the same day.

The setup, step by step

  1. Open your client's MCP or connector settings. Claude, ChatGPT, Grok, Cursor and every other MCP host keep this in a different menu; zambo.dev/add lists the exact clicks per client. This is the slow step, and it is still just navigation.
  2. Paste the URL. Add https://zambo.dev/mcp as a remote MCP server. One URL, no key: nothing is installed automatically and no credential is created.
  3. Make one call. Ask your agent to use any Zambo tool. The result comes back with a verifiable AER-1 receipt at a public URL, the same object the demo produces.
  4. Check the receipt. Paste its ID into zambo.dev/verify. The verifier recomputes the commitment over the saved result; a match proves the saved result has not changed since it was saved. Setup is done when this check passes on a call your own agent made.

Building in a framework instead of a chat client takes the same order of time: one package install (for example aer1-pydantic for Pydantic AI, or the sibling packages for LangChain, CrewAI, the OpenAI Agents SDK and SmolAgents) or one MCP toolset registration pointing at the same endpoint.

What you are not doing

  • No server to run. The endpoint is hosted; receipts are recorded by the executing layer as calls run.
  • No logging pipeline to build. The receipt is created at execution time, not reconstructed later from transcripts your agent wrote about itself.
  • No migration. Your agent keeps its own tools; Zambo's arrive alongside them (153 tools on the full surface, 35 loaded by default), and you can receipt one call today and decide about the rest later.
  • No payment to start. The free tier covers 20 free calls per day. A Day Pass ($0.99) covers a full day of heavier work; the Zambo Pass ($29 for 30 days, one payment) covers ongoing use.

Proof it is really this short: a receipt from today

Receipt d6949ef2-d6f7-46ec-a902-cf8be1ebeb7a (tool memory_remember) was saved today, 2026-10-25T14:41:56.661Z, with output hash sha256:716f3d7dc745c642ab467e4c999bc8a918e990c1abce72607393a476093aeca1. Its public run page states the result has not changed since it was saved, and the commitment check on the page reads: commitment matched. Open it, then run the same check at zambo.dev/verify: that two-minute detour is the entire verification habit your agent's work picks up once it is connected.

The claim stays narrow on purpose. A receipt proves the saved result was not changed since it was saved. It does not prove the agent chose the right tool or that the result was correct. It settles what ran, with what arguments, and what came back.

Receipt setup: FAQ

How long does it take to set up receipts for an AI agent?

Minutes, and most of it is finding the settings screen in your client. The connect step is one paste: add https://zambo.dev/mcp as a remote MCP server in the AI client you already use, following the per-client steps at zambo.dev/add. There is no API key, no account, and nothing to install server-side. The first receipt is not a second step: it arrives with the result of the first call you make, because the record is created when the call executes. The live demo at zambo.dev/demo runs one real call and hands you its receipt in about 10 seconds, which is the round trip you are setting up.

Do I need an API key or an account to set up Zambo receipts?

No. The MCP endpoint at zambo.dev/mcp is keyless: you paste the URL into your client's connector or MCP settings and call the tools. The free tier covers 20 free calls per day with no account. Payment only enters when you want more than the free tier: a Day Pass is $0.99 for 24 hours, and the Zambo Pass is $29 for 30 days as one payment.

When does the first receipt appear?

With the first call's result. Receipts are created by the executing layer at the moment a call runs, not minted in a batch afterwards, so the first tool call your agent makes through Zambo returns its result plus a verifiable receipt at a public URL. You can check that first receipt immediately at zambo.dev/verify: paste the receipt ID and the verifier recomputes the commitment over the saved result.

What does it cost to keep receipts running after setup?

Nothing to start: the free tier covers 20 free calls per day. Past that, a Day Pass ($0.99, USDC on Base for agents, card or PayPal for humans) keeps every call receipted for 24 hours, and the Zambo Pass is $29 for 30 days as one payment ($290 for 365 days; $19 for 30 days for $ZAMBO holders). Every paid call carries the same AER-1 receipt as a free one.

Related