BitBooth is a multi-chain x402 payment gateway for AI agents. Thirteen paid HTTP endpoints, each advertising up to nine different (network, asset) tuples in its 402 challenge. The agent picks one based on which chain it actually holds liquidity on, signs the payment, and gets the response back. The full OpenAPI reference is embedded below. The cards underneath are quick orientation for first time visitors.
The fastest way to see the gateway in action is the interactive playground. Pick a chain, pick an endpoint, and watch a real 402 challenge come back in your browser. No wallet required for the demo flow on /v1/cdp/echo.
Install npm install @bitbooth/mcp-fetch for any MCP compatible agent (Claude Code, Cursor, Continue, Windsurf), or wire your own client by following the agent setup guide. The HTTP flow is the same for any language.
Three JSON surfaces let agents enumerate paid routes without scraping. The bazaar catalog lives at /bazaar.json, the well known mirror at /.well-known/x402.json, and the A2A agent card at /.well-known/agent.json.
Agent calls a paid endpoint with no payment. Gateway returns HTTP 402 with the multi chain accepts[] array. Agent picks one entry, signs the payment (EIP-3009 for EVM stablecoins, ed25519 for SVM and XRPL native, Stellar envelope for Stellar, on chain transfer then reference for LINK and XRPL EVM), retries with the X-PAYMENT header. Gateway verifies, settles via the right facilitator, runs the handler, returns the response.
Base mainnet (USDC, LINK), Solana mainnet (USDC SPL), XRPL native (XRP, RLUSD, USDC IOU), Stellar pubnet (XLM, USDC), and XRPL EVM Sidechain (native XRP). See the Networks section on the home page for the full table with facilitator and issuer attribution.
Below is the full Swagger UI for the gateway. Every endpoint, request shape, response shape, status code, and example. Click any operation to expand, then click Try it out to fire a real request from the page. Raw spec at /openapi.yaml.