Burnbound documentation
Burnbound is a buyer-side spending control plane for AI agents that pay x402 APIs. Before an agent pays, Burnbound checks the payment against rules a human set (allowed hosts, per-payment and daily caps, human approval above a threshold); only allowed payments are signed, by a wallet the customer brings. Burnbound never holds private keys or funds.
- Quickstart: Claude Code and Cursor
From creating an agent key in the dashboard to the agent's first fetch_paid call, in Claude Code or Cursor.
- Concepts
Policies, per-payment and daily caps, allowed hosts, human approvals, signing modes and the x402 v2 payment flow.
- MCP tools reference
Configuration, the fetch_paid, get_budget, list_payments and get_approval_status tools, error codes and the wallet CLI of @burnbound/mcp.
- SDK
Status of the JavaScript SDK (payFetch and wrapFetchWithPayment): not published on npm yet; use the MCP server today.
- Security and trust model
What Burnbound stores and sees in each signing mode, the cooperative limit of client-side signing, and out-of-policy detection.
- FAQ
Short answers about wallets, networks, fees, plans, custody and supported agents.
For LLMs and agents: /llms.txt lists every page, and /llms-full.txt has all of them as one Markdown file.