BitBooth

Documentation

BitBooth is a multi-chain x402 payment gateway for AI agents. 40 paid HTTP endpoints can advertise up to five correctly quoted, request-bound signed stablecoin tuples when all recipients and issued-asset opt-ins are configured. The agent picks one based on which chain it 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.

40 paid endpoints 4 networks 3 settlement paths (CDP, T54, self-hosted Stellar) up to 5 signed stablecoin tuples per call x402 v2 protocol MIT licensed

Start here

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.

Pay from your own agent

The PageDelta-capable MCP buyer 2.3.1 is public on npm and clean-install verified; official MCP Registry publication is pending separate approval and public readback. Use the version-pinned npm install @bitbooth/mcp-fetch@^2.3.1 command shown in the agent setup guide. Credential-free installs expose only free discovery and preflight; the HTTP discovery flow is also available in any language.

Machine discovery

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 BitBooth capability manifest at /.well-known/agent.json.

x402 payment flow

Agent calls a paid endpoint with no payment. Gateway returns HTTP 402 plus the base64 PAYMENT-REQUIRED header and multi-chain accepts[] array. The agent picks one entry, creates its request-bound signed proof (EIP-3009 on Base, a signed SVM transaction on Solana, a signed XRPL transaction, or a Stellar envelope), and retries with PAYMENT-SIGNATURE. The gateway verifies, settles through the right path, runs the handler, and returns the response with PAYMENT-RESPONSE. X-PAYMENT is a compatibility alias, not the canonical v2 name.

Chain coverage

Base mainnet (USDC), Solana mainnet (USDC), XRPL native (RLUSD and Circle USDC IOU), and Stellar pubnet (Circle USDC). Native XRP/XLM are disabled until an expiry-bound FX quote derives a value-correct amount; transaction-hash-only LINK and XRPL EVM rails are also disabled. See the Networks section for facilitator and issuer attribution.

The OpenAPI spec

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.


↓ Full OpenAPI reference below ↓