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

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. Free tier included; limits vary by tool.

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 153-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"])

What Zambo is

Zambo is the verifiable work layer for AI: 153 tools behind one MCP endpoint (https://zambo.dev/mcp), 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.

Free tier, honestly

• Free: 20 free calls per day. 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/mo or $290/yr ($19/mo for $ZAMBO holders). Never required for a first call.

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

Commands

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).