Using bazaar.tools from an MCP client

The fastest way to call bazaar.tools is not to call it directly. Connect your agent to the Bazaar MCP server and it will discover us through Coinbase’s catalogue and call us on your behalf.

Discovery

The Bazaar MCP server exposes a search_resources tool. Asking it for “flight itinerary search”, “daily stock OHLC”, or “trending topics on X” returns our endpoint as one of the candidates, ranked by recency and buyer-reach signals.

Invocation

Once your agent has selected a resource, it calls proxy_tool_call with the resource ID and an input matching the published inputSchema. The MCP server handles the entire x402 dance — signing the upto authorisation from your funded wallet, retrying with PAYMENT-SIGNATURE, surfacing the response. Your agent never sees a 402 or a signing prompt.

What we publish

Every endpoint in our catalogue ships full Bazaar metadata:

• A semantic description (1–2 sentences).
• A strict JSON Schema for the input.
• A realistic output example + the output JSON Schema.

That metadata is the contract your agent integrates against. The same metadata drives our docs reference pages — change the spec once, the Bazaar listing, the docs page, and the runtime validator all update together.