Loading
Loading
Practical guides to letting AI agents refund, buy and pay APIs with spending limits, human approvals and no custody.
Run the Burnbound action gateway with your restricted Stripe key so an agent's refunds pass its caps, approvals and rules before they reach Stripe.
Put the Burnbound action gateway on Render, Railway, Fly.io or Docker Compose from the panel's assistant, then prove it with check before the first refund.
Let Stripe ask Burnbound before every charge on an agent's Issuing card: caps, allowed merchants and rules in real time, with no Stripe key stored.
The controls that bound what an AI agent can pay: per-payment and daily caps, allowed hosts, per-call limits, human approval and wallet balance.
Make an AI agent wait for a human above a USD threshold, get a Slack message for each payment, and let the agent retry safely once approved.
Step by step: give Claude Code a daily cap and a list of allowed hosts, then let it pay a real x402 API such as Exa search in USDC.
What an x402 MCP server does, the eight tools of @burnbound/mcp, and how to install it in Claude Code and Cursor with your agent key.
Where the key lives, who can sign and what an agent with shell access can do, for a Coinbase CDP wallet and a key on your own machine.
The x402 v2 payment flow from the buyer's side: the 402 challenge, the EIP-3009 signature, the retry, and why the buyer never calls settle.