Zzambo
A clear, sourced snapshot

Zambo by the numbers

Zambo is the verifiable work layer for AI. Check work receipts, carry memory between AIs, and pick up where you left off. Live figures and sources below.

Add Zambo to your AISee a live receiptRead the MCP overview

Created and run by Brennan Zambo, solo founder. Flagship capability: HANDOVER, to carry saved work into another AI.

Live product activity

Sources: /api/stats · package totals ·
Receipts issuedAll time, from live stats
Receipts todayUTC day, from live stats
All-time package downloadsLoading live public registry totals
Total tool callsFrom live stats

Totals load directly from public registry sources.

Calls and receipts count activity, not unique people. Live figures load from their source APIs and refresh in this page.

Work tool calls: · live products across the Zambo estate.

Public registry data

Lifetime downloads, clearly sourced

Counts come from public APIs, not Zambo self-report. PyPI plus npm form the package total. Hugging Face datasets are separate. Downloads are not people.

Python · PyPI
all-time downloads across live package listings
As of

Source: PyPI Stats public dataset, with mirrors. Open package data.

View all PyPI packages
PackageLatest versionDownloads
JavaScript · npm
all-time downloads since package creation across packages
As of

Source: npm downloads API, package lifetime totals. Open package data.

View all npm packages
PackageLatest versionDownloads

Waiting for current public registry totals. Figures refresh within 15 minutes.

What Zambo does

Receipts, memory, and a clean handoff

Zambo works beside the AI you already use. It records tool results, recalls saved notes, and helps another AI resume the task.

Proof of work

A receipt stores a tool result and lets you check whether that saved result changed. It does not tell you whether the answer was correct. Check a receipt.

Private memory across AIs

Save a useful fact once, then retrieve it with your caller handle or private memory code in another connected AI. Private memory stays scoped to its owner.

Wrap up and keep going

HANDOVER carries the goal, notes, links, and next step into another AI. Add Zambo to your AI.

Open standard

AER-1, with public conformance data

  • Internet-Draft: draft-zambo-aer1, revision -26Closed at revision -26. Active draft.
  • draft-zambo-aer1-wimse-mapping, revision -02Posted 2026-11-01.
  • draft-zambo-aer1-audit-data-model, revision -00Active draft.
  • Conformance corpus: 143 vectors, 146 checksKit v1.5.7. Open the corpus JSON.
How to read these figures

Sources and method

Package downloads come from the public PyPI Stats dataset and npm downloads API, not Zambo self-report. PyPI includes all-time downloads with mirrors; npm counts each package from its creation date through npm’s latest available reporting day. Hugging Face uses the official downloadsAllTime field, reported separately.

Receipt and call counts come from the live Zambo stats API. “Today” means the current UTC calendar day. MCP catalog size is read from the current catalog.

A receipt records a saved result and lets anyone check whether it has changed since it was saved. It does not establish that the result is correct.

Free access includes 20 calls each day, shared across work tools, and one free wrap-up a day. Pickup in another AI is always free.

Paid access removes Zambo’s shared daily call cap: $0.99 for 24 hours or $29 for 30 days, one-time. Individual tool and provider limits still apply. No subscriptions.

One connection. A clear starting point.

MCP endpoint: zambo.dev/mcp

The default MCP surface has 36 tools. The full catalog has 153. The catalog can change; these counts come from live stats.

Package downloads do not represent active users. The numbers above count saved receipts and tool activity, not unique visitors.

Put your AI to work with proof and continuity.

One connection for receipts, memory, and handovers. Free to start.

Add Zambo to your AI