Your AI agent can now pay. Who set the budget?
AI agents can now pay for data and APIs on their own. Before yours does, set three limits: a cap, a wall and a log.
Abhijit Chatterjee Chattopadhyay

The web has always had an error code for "pay me first": 402 Payment Required. For most of its life it sat reserved for future use (opens in a new tab).
The future arrived. AI agents now answer it, and pay.
What changed
x402 (opens in a new tab) is an open standard for payments over plain web requests. A server replies 402 with a price and a payment address. The agent pays and asks again. No form, no card, no human.
It is not a toy. On 16 October, the x402 site showed 75.41 million transactions and $24.24 million in volume over the previous 30 days.
And the big platforms are wiring it in. On 13 October, AWS showed agents in Anchor Browser paying for x402 pages and APIs through Amazon Bedrock AgentCore payments (opens in a new tab), inside a budget, with every payment logged.
What can go wrong
The same AWS post names the first two risks plainly, and makes the third a requirement:
- Runaway spend. A bug, a retry loop or a prompt injection can keep paying until someone notices.
- Exposed keys. If the wallet key lives inside the agent, it sits next to untrusted web pages and third-party tools.
- No trail. Without a record of every attempt, approval and refusal, you cannot reconcile what was spent or why.
An agent that loops on a paid endpoint does not get tired. It just keeps paying.
Cap, wall, log
Before any agent of yours touches money, put three things in place:
- Cap. A spending limit per task and per day, enforced outside the agent, in the payment layer. Not a line in the prompt.
- Wall. The agent never holds the keys. It asks a separate service to pay, and that service can say no.
- Log. Every payment attempt, approval and refusal is recorded, and someone reads it weekly.
If your setup cannot do all three, the agent does not get a wallet yet.
Do this today
- List every paid API or data source your agents could call.
- Set a hard cap for each, starting low enough that a runaway loop is an annoyance, not an incident.
- Check where the payment keys live. If the answer is "in the agent's environment", move them.
- Name one person who reads the payment log.
Your next step
I write one practical note like this every day. Sign up just below to get them by email.
Drafted with AI help, edited and approved by me.