zambo-sdk
Thin Python client for Zambo, the verifiable work layer for AI. 153 tools behind one MCP endpoint, a verifiable AER-1 receipt for every call. Free tier included: 20 free calls per day. No account, no API key. Zero dependencies.
Install
pip install zambo-sdk
Quickstart
from zambo_sdk import Client, verify_receipt
z = Client()
# 1. Call a tool: plain JSON-RPC, no API key
result = z.call("live_price", {"symbol": "BTC"})
print(result.text)
print("receipt:", result.receipt_id)
print("audit: ", result.audit_url)
# 2. Route any goal through the universal entry point
job = z.universal("audit https://example.com for AI discoverability", session="demo-1")
print(job.text)
# 3. Search the full 153-tool catalog
found = z.search("generate QR code")
print(found.text)
# 4. Verify a receipt client-side (recomputes the sha256 locally)
v = verify_receipt(result.receipt_id)
print("verified:", v.verified, v.checks)
API
Client().call(tool, arguments)->CallResult(.text,.receipt_id,.audit_url,.receipt)Client().list_tools()-> list of tool descriptorsClient().search(query)-> search the full catalog viacapability_searchClient().universal(goal, session=None)-> multi-step jobs viazambo_universalget_receipt(receipt_id)-> full receipt JSONverify_receipt(receipt_id)->Verification(.verified,.checks,.audit_url)
verify_receipt checks three things: the receipt exists, the server marks it verified, and, recomputed locally so the server can't fake it, sha256(canonical_bytes) == output_hash, plus the presence of the anchor record. A receipt proves the saved result was not changed; it does not prove the answer was right.
Receipts follow AER-1 (IETF Internet-Draft draft-zambo-aer1-26). Multi-step jobs can be packaged as a handover: one link a reviewer opens to walk the steps and record a decision.
Notes
- Endpoint:
https://zambo.dev/mcp(JSON-RPC 2.0 over HTTPS,streamable_http-compatible). - Receipts: audit page
https://zambo.dev/run/<uuid>; verify any receipt at https://zambo.dev/verify/. - Need more than the free tier? The $0.99/24h Day Pass is at zambo.dev/day-pass.
Metadata
Release files for zambo-sdk 0.1.5
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_sdk-0.1.5.tar.gz | 5.2 kB | Without provenance | Details for zambo_sdk-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zambo_sdk-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for zambo_sdk-0.1.5-py3-none-any.whl |
Total release size: 10.8 kB
Release files / zambo_sdk-0.1.5.tar.gz
| Download URL | zambo_sdk-0.1.5.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1de8c773cc15d79f154801717469a8d66345e397883b5cc64c8df54d2d53e750
|
|
BLAKE2b-256 checksum How to use checksums |
ebd834d5b391e4f6e1156eb72e1008785c232f873d906af5c9cada30c0b0688f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Release files / zambo_sdk-0.1.5-py3-none-any.whl
| Download URL | zambo_sdk-0.1.5-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08cb6a25ef1788a29545e76046250fdcc0284e77aa91dd88fc1b659b4644af69
|
|
BLAKE2b-256 checksum How to use checksums |
bdc448a95bf0825f228591b8ff1632a15ad9a1f32a90663c56e7cf9c3484a76b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
rambo-pypi-grab/0.1.0
|
Security for zambo-sdk 0.1.5
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.