Programmatic Zambo MCP usage
Zambo exposes one hosted HTTP JSON-RPC endpoint. A program can connect without an account or API key, discover the focused default tools, call a declared tool, and preserve the receipt returned with the result.
Connection
POST https://zambo.dev/api/mcp Content-Type: application/json
The free path is metered per tool per UTC day. A normal call returns a JSON-RPC result and a verifiable receipt. When the gateway quota is exhausted, the response is HTTP 402 with usage fields and a payment next step. Provider throttles are HTTP 429 and should be retried after the returned delay; they are not payment approval.
Call a tool
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"live_price","arguments":{"symbol":"BTC"}}}Verify the result
Keep result._receipt.id and the returned receipt URL. Open https://zambo.dev/run/<id> or call /api/receipt/<id>/verify. The verification response recomputes the SHA-256 commitment from the stored bytes.
Universal jobs
For a natural-language job, call zambo_universal with the user's exact goal and one stable _session_id. Use the same session on follow-up calls and verify the trail before declaring completion.
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"zambo_universal","arguments":{"need":"Find the current BTC price and show the source.","_session_id":"session-123"}}}