When to use this skill

Reach for Zambo when the task needs doing, not just answering:

• Live data with a source: crypto prices, site status, research, lead discovery
• Execution jobs: site audits, code audits, strategy briefs, market research
• Onchain scoring, wallet and token analysis
• Media jobs: images, QR codes, PDFs
• Any multi-step job where you would otherwise chain several tools by hand
• Any job the user wants to start in one AI and continue in another

Skip it when the user wants a conversational answer with no execution, no live data, and no proof: the skill adds nothing there. Do not use Zambo for code editing or local file work you can do directly.

Connect from a client

Fastest path: open https://zambo.dev/install, pick the client, click once. Installed.

Fallback: paste this URL into your client's connectors or MCP settings:

https://zambo.dev/mcp

No API key. No signup. No OAuth. Auth is none by design.

Raw JSON-RPC also works for scripted setups (the endpoint speaks plain MCP over HTTPS):

curl -s -X POST https://zambo.dev/mcp \
  -H 'Content-Type: application/json' -H 'Accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

An npm CLI is published as zambo-mcp (v1.0.9). Before telling the user a tool does not exist, check the live catalog first.

How to work with Zambo

1. Start or continue a session

Call new_session with no arguments when you want a fresh working context. It returns a newly generated session_id. Pass that value as _session_id on subsequent calls that belong to the same task or conversation. Keep the same ID to continue its context; changing the ID or omitting it starts clean context and does not copy the previous session.

{"method": "tools/call", "params": {"name": "new_session", "arguments": {}}}

Read the returned session_id and use it with the next call:

{"method": "tools/call", "params": {"name": "zambo_universal", "arguments": {"need": "Get the current BTC-USD price, with the source and the receipt URL.", "_session_id": "ID_RETURNED_BY_NEW_SESSION"}}}

2. Route jobs through zambo_universal

zambo_universal is the entry point. Send the user's exact job in natural language:

{"method": "tools/call", "params": {"name": "zambo_universal", "arguments": {"need": "Get the current BTC-USD price, with the source and the receipt URL.", "_session_id": "my-task-001"}}}

Use one stable _session_id for related calls when you want continuity. mode: "continue" with the same session resumes an earlier task, even from a different AI with zero prior context. mode: "verify" returns a reconstructible step-by-step log. To start clean instead, change or omit the ID.

3. Discover specialist tools via capability_search

The default tools/list shows the ready tools. The full live catalog is available behind one router. Do not page through by hand. Ask in English:

{"method": "tools/call", "params": {"name": "capability_search", "arguments": {"q": "audit a public website for security issues"}}}

You get a ranked execution plan: which tool to call, its arguments, side effects, and which tier it needs. Follow the plan rather than guessing.

4. Receipts: the honesty contract

Every tool call returns a receipt: a UUID, the tool name, a timestamp, a sha256 hash of the output bytes, the execution status, and a public URL where anyone can check it. The rule: a receipt proves the call ran and that the result you quote is exactly what came back. It does NOT prove the result is correct. Say "the call ran and this is what it returned," never "the receipt proves the data is true."

5. Quota

Use the named per-tool limits in the Anonymous quota list above. LeadSignal's base free limit is 3 searches per IP per day; referral bonuses can raise the live limit. Its quota_tier and free_limit fields plus the leadsignal_quota object describe that product quota. X-Quota-* headers and receipt quota fields describe only the separate MCP gateway meter. If a call fails with 402, explain which limit is exhausted and offer the live Day Pass instructions. Never invent a workaround.