Amazon took AgentCore Payments out of preview on Tuesday, giving agents built on Bedrock the ability to find a paid API, pay for it in stablecoins and keep working — with spending caps enforced by the platform, not the prompt. Thursday, Binance switched on Agent OS, which lets agents running through ChatGPT, Claude Code, Codex and Cursor trade through dedicated sub-accounts with permissions the account holder sets. Two of the largest platforms in cloud and crypto shipped agent money within 48 hours of each other.
The plumbing underneath both is the same old idea: HTTP status code 402, “Payment Required,” reserved in the web’s specification since the 1990s and almost never used, because humans pay through checkout pages, not status codes. Under the x402 protocol, an agent that hits a paid endpoint gets a 402 response, negotiates the price, authenticates a wallet — AWS wires in Coinbase and Stripe’s Privy — settles in stablecoins and collects proof of payment, all without leaving its reasoning loop. No card form, no human, no interruption.
Binance’s version is scoped like a trainee’s desk, not a trading floor. Agents get dedicated sub-accounts, the owner chooses what they can touch — spot, futures — withdrawals are blocked by default and access can be pulled at any time. Reported default caps run $50,000 a day for regular swaps and $100,000 for DeFi transactions, but just $20 a day for x402 payments. The product launched without the European Economic Area. TechCrunch’s read on the whole arrangement: keeping the agents in check is largely up to the user.
The last missing primitive
None of this arrived from nowhere. Cloudflare launched Kitesurf, a browser runtime built for agents that uses a fraction of Chromium’s compute, on 6 August — alongside its own x402 support, with more than 20 companies already in those agent-initiated payment flows. Agents already generate the majority of the traffic Cloudflare sees. MCP standardised how agents reach tools. Auto-approval defaults are cutting humans out of routine confirmations. Browsing, tools, autonomy — the agent stack was complete except for money. Three platforms filled that gap in the same month.
Our take: Look at where every one of these products puts the spending limit: in the infrastructure, below the model. Nobody who just shipped agent money trusts the agent — the caps, blocked withdrawals and revocation switches are the product. And note the ratio at Binance: $50,000 a day on rails the exchange has run for years, $20 a day on the brand-new machine-to-machine one. The newer the pipe, the tighter the leash. If you run a business: treat an agent wallet exactly like a corporate card for a first-week hire — smallest cap that does the job, logging on from day one, and test the revoke button before you need it.
What to watch
- Whether the model vendors follow. OpenAI, Anthropic and Google are watching other platforms attach wallets to their agents. A native wallet inside ChatGPT or Claude would change who holds the caps — and who holds the liability.
- The x402 headcount. Twenty-plus companies is a pilot, not an economy. The signal worth waiting for is a major card network or a mainstream payments processor joining beyond Stripe’s crypto arm.
- Europe. Agent OS launched without the EEA in the first month of active EU AI Act enforcement. Whether agent payments can clear European rules decides if this becomes global plumbing or a regional experiment.
- The first public overspend. Somewhere, an agent will buy the wrong thing at volume. Who eats it — user, platform or model vendor — is unwritten case law, and the drafting just started.
The web spent thirty years with a payment error nobody threw. It took customers who aren’t human to make it useful.