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/
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.
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"])
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: 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 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/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
| 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 3,991 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
- zambo-swarm: use it when the job is bigger than one agent and several workers must each prove their piece of one shared job. PyPI: https://pypi.org/project/zambo-swarm/ and npm: https://www.npmjs.com/package/zambo-swarm
- zambo-loop: use it when an agent must pick up its own work tomorrow, recall its baseline verbatim, and keep one job alive across sessions. npm: https://www.npmjs.com/package/zambo-loop (PyPI listing pending)
- zambo-verify-pass: use it when someone retells a result and you need to catch the drift against the receipt of record. PyPI: https://pypi.org/project/zambo-verify-pass/ and npm: https://www.npmjs.com/package/zambo-verify-pass
- zambo-delivery: use it when a client must check delivered work step by step and their pickup is the sign-off. PyPI: https://pypi.org/project/zambo-delivery/ and npm: https://www.npmjs.com/package/zambo-delivery
- zambo-watch: use it when one watcher checks the same signal on a schedule and must prove what it saw, quiet days included. PyPI: https://pypi.org/project/zambo-watch/ and npm: https://www.npmjs.com/package/zambo-watch
Metadata
Release files for zambo 1.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zambo-1.0.13.tar.gz | 14.2 kB | Without provenance | Details for zambo-1.0.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zambo-1.0.13-py3-none-any.whl | Python 3 | none | any | Details for zambo-1.0.13-py3-none-any.whl |
Total release size: 26.9 kB
Release files / zambo-1.0.13.tar.gz
| Download URL | zambo-1.0.13.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ae8ab69bd6b940bcd5190a1f1e1ba1be211305e201443b769c90a2520e25c3f
|
|
BLAKE2b-256 checksum How to use checksums |
7865cb36dda045dfe12fa9358e7369c3355cbd751d05e6e9b0d7685ce4f7f7fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Release files / zambo-1.0.13-py3-none-any.whl
| Download URL | zambo-1.0.13-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
889a4c9cc595716518218ffadd560a762043cb3defaa6e551fa78c99f7ece57e
|
|
BLAKE2b-256 checksum How to use checksums |
0697e74de0103ea4570c37b7092f4833a79efb6a1baa5fa615f6d61bb7ceb036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Security for zambo 1.0.13
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.