Skip to main content

zambo: the verifiable work layer for AI, on your command line

AER-1, the agent execution receipt standard: zambo.dev/aer-1 | Add Zambo to your AI: zambo.dev/add/

Try it now, no install: the live demo �� check any receipt at zambo.dev/verify/.

Definitions: What is AER-1? �� What is a verifiable execution receipt?

The problem: AI models talk. Getting things done, checking a live price, auditing a site, running research, pulling data, means wiring up APIs, keys, and glue code for every single task.

The fix: one command. Describe the job, get it done, get a receipt.

pip install zambo
zambo "what's the price of BTC right now?"
BTC $81,235.00 USD ...

receipt 89ccbddc-0b3b-4dbd-b424-4ee75119ef80
audit: https://zambo.dev/run/89ccbddc-0b3b-4dbd-b424-4ee75119ef80
verify: zambo verify 89ccbddc-0b3b-4dbd-b424-4ee75119ef80

No account. No API key. No config. 20 calls + 1 wrap-up free every day. Picking up in another AI is always free. Call 21 is where a job outgrows the free tier: the Day Pass is $0.99 for 24 hours unlimited, and picking up in another AI is always free.

Quickstart

# One-command: describe any goal
zambo "audit example.com for AI discoverability"

# Call a specific tool directly
zambo call live_price '{"symbol":"BTC"}'
zambo call ghost_audit_site '{"url":"https://example.com"}'

# Search the tool catalog
zambo search 'generate QR code'

# List exposed tools
zambo list

# Verify any receipt
zambo verify 89ccbddc-0b3b-4dbd-b424-4ee75119ef80

# Teach your agents about Zambo (writes to AGENTS.md / CLAUDE.md / .muserules)
zambo init

Or use it from Python:

import zambo

out = zambo.call_tool("live_price", {"symbol": "BTC"})
print(out["text"], out["receipt"]["id"])

v = zambo.verify_receipt(out["receipt"]["id"])
print(v["verified"], v["sha256"])

Connect any MCP client in one paste

{
  "mcpServers": {
    "zambo": {
      "url": "https://zambo.dev/mcp"
    }
  }
}

Paste that into your client's MCP config (Cursor, VS Code, Windsurf, Claude Desktop), or add Zambo in one step at https://zambo.dev/add/ . Every call returns a verifiable receipt; check any receipt at https://zambo.dev/verify/ .

Make it a daily loop

Give an agent a standing routine and Zambo stops being a one-off call and becomes its daily habit. At the start of each run it picks up its continuity for free and recalls what it remembers. It does the work. At the end it wraps the job in a handover, so the next run, in this AI or another one, starts exactly where this one stopped. The whole loop fits the free tier alone: 20 calls + 1 wrap-up free every day, and picking up in another AI is always free.

Proof from a real scheduled run: the wrap receipt. The full recipe: the scheduled agent heartbeat.

What Zambo is

Zambo is the verifiable work layer for AI: 153 tools behind one MCP endpoint (https://zambo.dev/mcp), 37 on the default surface,, over plain JSON-RPC. Live crypto prices, site audits, web research, content tools, lead and data tools, multi-step agent jobs, and handover, the flagship: finished work passed from one AI to the next as a chain of steps, each with its own receipt, ready for client sign-off. This package is a thin Python client for that endpoint (stdlib + requests only).

Don't know which tool fits? Skip the catalog: zambo "<goal>" routes through zambo_universal, which picks the right tools for the job. Pass --session <id> to keep a trail across calls.

Receipts: proof the saved result was not changed

Every call returns a verifiable receipt: a UUID, a timestamp, and a sha256 of the saved result, in the AER-1 format (IETF Internet-Draft draft-zambo-aer1-26). Anyone can recompute the digest and check that the saved result is exactly what was saved when the call ran.

Honest scope: a receipt proves the saved result was not changed. It does not prove the answer was right. It fixes the record; judging the work stays with you.

Check any receipt in your browser or on the command line:

zambo verify <receipt-uuid>     # confirms zambo.dev serves the receipt,
                               # and shows sha256, source, timestamp, audit URL

Receipt pages are real web pages with Open Graph tags and canonical URLs, shareable, linkable, citable.

Try the Receipt Test: run a free call, get a receipt, verify it yourself.

When you hit the daily free limit

You get 20 calls + 1 wrap-up free every day, and picking up work in another AI is always free. Call 21 is where a job outgrows the free tier: the Day Pass is $0.99 for 24 hours unlimited, and picking up in another AI is always free. When the free calls run out mid-job, the next call is refused and does not run. That refused call still issues a receipt for the wall response, and it burns no quota, so the job record stays intact and nothing already saved is lost.

To keep going the same day, get a Day Pass: $0.99 for unlimited calls for 24 hours, including unlimited wrap-ups. If you are an agent, pay programmatically: the wall response itself carries an x402 payment, settled in USDC on Base, and the pass activates when that payment settles. If you are a human, pay by card or PayPal at https://zambo.dev/day-pass/ and the pass activates the same way.

If you run Zambo every day, the Pass is $29 per 30 days. Day Pass and Pass are one-time payments.

Free tier, honestly

  • Free: 20 calls + 1 wrap-up free every day; picking up in another AI is always free. No account, no API key, no card.
  • Paid: the $0.99 Day Pass (24h) at zambo.dev/day-pass: humans pay by card or PayPal, agents pay with USDC on Base via x402. The Zambo Pass is $29 for 30 days ($19 for verified $ZAMBO holders), or a Lifetime Pass at $250, one payment. Full pricing: https://zambo.dev/pricing Never required for a first call.

No fake limits, no "contact sales to see a price."

Commands

Command What it does
zambo "<goal>" [--session <id>] Do the thing. Routes via zambo_universal.
zambo call <tool> '<json>' Call one tool directly.
zambo search '<query>' Search the tool catalog.
zambo list List exposed tools with one-line descriptions.
zambo verify <receipt-uuid> Verify a receipt on zambo.dev.
zambo init [--root <dir>] [--file <name>] [--force] Write the Zambo section into your project's agent instruction file.

Requirements & troubleshooting

  • Python 3.8 or newer. Only dependency: requests.
  • The upstream endpoint occasionally resets connections; the client retries transient transport failures automatically (up to 4 attempts). A received JSON-RPC error is never retried; it's shown to you as-is.
  • Timeouts: 60s per attempt.

License

MIT: see LICENSE (included in the package). Built by Zambo (Brennan Zambo, solo founder).

Where these receipts run live: Zambo

The zambo CLI puts the live Zambo endpoint in your terminal, every call returning a verifiable AER-1 receipt, and it has been downloaded more than 8,700 times on PyPI. The live home of those receipts is Zambo, the verifiable work layer for AI. Connect any AI to the live endpoint at https://zambo.dev/mcp or add Zambo to your AI in one step at https://zambo.dev/add/

Free tier: 20 calls + 1 wrap-up free every day; picking up in another AI is always free. The Day Pass is $0.99 for 24 hours, unlimited.

Install:

pip install zambo

The Zambo pattern family

Five installable packages teach Zambo patterns, each with a real run behind it. The family page: https://rambozambodotdev.gitlab.io/aer1-hub/the-pattern-family.html

Semantic Kernel (Microsoft)

Every Semantic Kernel function call, journaled as it happens, sealed into a verifiable AER-1 receipt when the session wraps:

from semantic_kernel import Kernel
from zambo.semantic_kernel import ZamboSession, add_zambo

session = ZamboSession()
kernel = Kernel()
add_zambo(kernel, session)   # ZamboReceipts plugin + auto-journal filter

# ... run your kernel functions as usual ...

print(session.wrap(summary="what the agent did",
                   goal="the original goal",
                   recipient="whoever picks this up next"))
# -> https://zambo.dev/run/<receipt-id>

The filter journals each invocation's name and a SHA-256 of its result (results are hashed, never uploaded in full). The plugin adds verify_receipt, wrap_session, and session_status as native kernel functions. Proven live: a journaled Semantic Kernel session wrapped to https://zambo.dev/run/c87b1271-9f4d-4c3b-82f2-a86fe46c6dbc

Also available for LangChain, LangGraph, LlamaIndex, CrewAI, AutoGen, the OpenAI Agents SDK, PydanticAI, smolagents, Haystack, Google ADK, AWS Strands, and Agno, plus the Vercel AI SDK and n8n on the JS side.

CAMEL-AI

Every tool call a CAMEL ChatAgent makes, journaled as it happens from the step's own records, sealed into a verifiable AER-1 receipt:

from camel.agents import ChatAgent
from zambo.camel import ZamboSession, add_zambo

session = ZamboSession()
agent = add_zambo(ChatAgent(...), session)   # wrapped agent + ZamboToolkit

# ... call agent.step(...) as usual; tool calls journal automatically ...

print(session.wrap(summary="what the agent did",
                   goal="the original goal",
                   recipient="whoever picks this up next"))
# -> https://zambo.dev/run/<receipt-id>

The wrapper reads each step's tool_call_records (tool name + a SHA-256 of the result; results are hashed, never uploaded in full). The toolkit adds verify_receipt, wrap_session, and session_status as native CAMEL tools. Proven live: a journaled CAMEL session wrapped to https://zambo.dev/run/3ed95774-d210-4885-a31b-a5f54bb23cd8

Letta

Letta agents run server-side, so Zambo wraps the one seam every Letta app shares: the client message flow. Every tool call in a send_message response, journaled as it happens, sealed into a verifiable AER-1 receipt:

from letta_client import Letta
from zambo.letta import ZamboSession, wrap_client

session = ZamboSession()
client = wrap_client(Letta(...), session)

# ... call client.send_message(agent_id, messages=[...]) as usual ...

print(session.wrap(summary="what the agent did",
                   goal="the original goal",
                   recipient="whoever picks this up next"))
# -> https://zambo.dev/run/<receipt-id>

The wrapper pairs each response's tool_call and tool_return messages (tool name + a SHA-256 of the return; returns are hashed, never uploaded in full). Proven live: a journaled Letta session wrapped to https://zambo.dev/run/4e7edfa3-3e8a-4794-a2ae-e11a698c9d5c

Metadata

Release files for zambo 1.0.26

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zambo 1.0.26
File Size Uploaded Provenance Actions
zambo-1.0.26.tar.gz 25.7 kB Without provenance Details for zambo-1.0.26.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for zambo 1.0.26
File Interpreter ABI Platform Actions
zambo-1.0.26-py3-none-any.whl Python 3 none any Details for zambo-1.0.26-py3-none-any.whl

Total release size: 49.1 kB

Release files / zambo-1.0.26.tar.gz

Download URL zambo-1.0.26.tar.gz
Size 25.7 kB
Tags Source
SHA-256 checksum
How to use checksums
17df8a5bc48d50b674a3bd23bae98df69082249ce6284cd0ed707b8306bbba57
BLAKE2b-256 checksum
How to use checksums
3eec8a62a246c457e5a4479b5d2a7e3dde647cccacc2b3f04089a99761b4cf34
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Release files / zambo-1.0.26-py3-none-any.whl

Download URL zambo-1.0.26-py3-none-any.whl
Size 23.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
458240ebb0467c465a182632975eff49cd92c7901c0ad50a54a421ca34ab3a32
BLAKE2b-256 checksum
How to use checksums
869b7c1fb6e6bc96952c77ceb34a206006e7adf13b68221087c58b6e083be4f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via rambo-pypi-grab/0.1.0

Security for zambo 1.0.26

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.26 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page