BitBooth MCP
Multi-chain x402 payment gateway enabling AI agents to pay per HTTP call with real on-chain settlement across 5 mainnet chains, providing 18 paid endpoints for utilities, data, and security.
README
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:
| Network | Asset | Facilitator |
|---|---|---|
| Base mainnet (eip155:8453) | USDC | Coinbase CDP |
| Base mainnet | Chainlink LINK | Self-hosted onchain verifier |
| Solana mainnet | USDC SPL | Coinbase CDP |
| XRPL native (xrpl:0) | XRP | T54 XRPL Facilitator |
| XRPL native | RLUSD (Ripple issuer) | T54 |
| XRPL native | USDC IOU (Bitstamp issuer) | T54 |
| Stellar pubnet | XLM | Self-hosted Horizon |
| Stellar pubnet | USDC (Circle issuer) | Self-hosted Horizon |
| XRPL EVM Sidechain (eip155:1440000) | Native XRP | Self-hosted onchain verifier |
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 challenge02-node-evm-pay.mjs— Node + ethers, signs EIP-3009 transferWithAuthorization on Base03-node-xrpl-pay.mjs— Node + xrpl.js, signs an XRPL Payment tx through the T54 facilitator04-mcp-config.json— drop-in MCP client config05-langchain-agent.py— LangChain agent that fetches paid URLs
The endpoint catalog
| Endpoint | Price | Category |
|---|---|---|
/v1/cdp/echo |
$0.001 | utility |
/v1/cdp/json-repair |
$0.001 | utility |
/v1/cdp/faker |
$0.001 | utility |
/v1/cdp/jwt-verify |
$0.001 | utility |
/v1/cdp/webhook-sig-verify |
$0.001 | utility |
/v1/cdp/llm-tool-validate |
$0.002 | utility |
/v1/cdp/pii-redact |
$0.002 | utility |
/v1/cdp/rss |
$0.002 | data |
/v1/cdp/dns |
$0.002 | utility |
/v1/cdp/ssl-info |
$0.002 | security |
/v1/cdp/x402-discover |
$0.005 | security |
/v1/cdp/agent-credit-score |
$0.005 | security |
/v1/cdp/wallet-doctor |
$0.005 | security |
/v1/cdp/prompt-injection-scan |
$0.005 | security |
/v1/cdp/contract-honeypot-check |
$0.005 | security |
/v1/cdp/approval-safety |
$0.05 | security |
/v1/cdp/render-pro |
$0.05 | data |
/v1/cdp/web-diff |
$0.08 | data |
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 examplesdocs/XRPL.md— XRPL native + XRPL EVM Sidechain integration notesopenapi.yaml— full OpenAPI spec for every paid endpointexamples/— 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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。