BitBooth

The multi-chain x402 payment gateway for AI agents. 18 paid HTTP endpoints, 5 mainnet chains, real on-chain settlement, ~$2/month to run on AWS Lambda.

Live: app.heinrichstech.com Playground: app.heinrichstech.com/demo API reference: app.heinrichstech.com/docs Bazaar manifest: app.heinrichstech.com/bazaar.json A2A agent card: app.heinrichstech.com/.well-known/agent.json

---

What is this?

BitBooth implements the x402 protocol — Coinbase's spec for "HTTP 402 Payment Required + on-chain settlement." Drop a paywall in front of any HTTP endpoint, and AI agents pay per call from their own wallet. No accounts, no API keys, no signups. Non-custodial — the agent pays your wallet directly, BitBooth never touches the funds.

1. Agent calls a paywalled endpoint with no payment
2. Server returns HTTP 402 with a multi-chain `accepts[]` array
3. Agent picks one entry (whatever chain it holds liquidity on) and signs
4. Agent retries the request with X-PAYMENT header
5. Server verifies + settles + unlocks the response

The whole loop is ~3 seconds on Base mainnet.

Why multi-chain?

Every BitBooth endpoint advertises up to 9 (network, asset) tuples in every 402 challenge:

Agents pick the chain they already hold. No bridging, no swaps, no friction.

Quick start

Pay one endpoint with curl (no payment yet — see the 402 challenge)

curl -s -X POST https://app.heinrichstech.com/v1/cdp/echo \
  -H 'content-type: application/json' \
  -d '{"message":"hello from agent"}'

You'll get back a 402 response body containing resource, accepts[], and an extensions.bazaar block.

Install the MCP server for any Claude / Cursor / Continue agent

npm install -g @bitbooth/mcp-fetch

Or in your MCP client config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "bitbooth": {
      "command": "npx",
      "args": ["-y", "@bitbooth/mcp-fetch"],
      "env": {
        "BITBOOTH_AGENT_KEY": "0x<your-testnet-wallet-private-key>"
      }
    }
  }
}

Testnet by default (Base Sepolia). Opt into mainnet explicitly with BITBOOTH_CHAIN_ID=8453.

Or build your own buyer

See examples/ for runnable demos:

• 01-curl-fetch.sh — pure shell, sees the 402 challenge
• 02-node-evm-pay.mjs — Node + ethers, signs EIP-3009 transferWithAuthorization on Base
• 03-node-xrpl-pay.mjs — Node + xrpl.js, signs an XRPL Payment tx through the T54 facilitator
• 04-mcp-config.json — drop-in MCP client config
• 05-langchain-agent.py — LangChain agent that fetches paid URLs

The endpoint catalog

Full schemas in openapi.yaml. Live manifest at /bazaar.json.

Documentation

• docs/INTEGRATION.md — integration guide (buyer + seller patterns)
• docs/ENDPOINTS.md — full endpoint catalog with examples
• docs/XRPL.md — XRPL native + XRPL EVM Sidechain integration notes
• openapi.yaml — full OpenAPI spec for every paid endpoint
• examples/ — runnable demos

About

BitBooth is built and operated by Heinrichs Software Solutions Company — a veteran-owned business based in Tallahassee, Florida. SDVOSB-pending, CAGE-registered, SAM.gov-registered. Solo-built. Production-grade testing (~2,400+ Vitest tests, 92% coverage on core payment + middleware paths). Approved under Anthropic's Cyber Verification Program for dual-use cybersecurity work.

License

MIT — see LICENSE.

This repository contains the public documentation, OpenAPI spec, and runnable examples for BitBooth. The gateway source code is operated privately during a federal-procurement-posture scrub; for technical-interview-grade source access, contact derek@heinrichstech.com.