The HTTP status code that swallowed a payment: how agents stalled on 402

When an AI agent hits a page or API priced per request — a premium dataset, a metered research endpoint, a paywalled publisher — the server returns HTTP 402 Payment Required. As AWS's machine learning blog frames it, the agent has no built-in payment mechanism, no budget attached to the session, and no programmatic way to satisfy the request. The task just stalls and waits for a human to sort it out. The proposed fix is a scheme called x402, which AWS describes as an open standard for HTTP-based machine-to-machine payments: the server returns the 402 with the amount, the accepted payment methods, and an address the agent can use to complete the transaction. Anchor Browser, a cloud browser-automation tool built for agents, has integrated with Amazon Bedrock AgentCore payments to let agents pay for x402-protected pages and APIs 'autonomously,' according to the vendor, and it's now on AWS Marketplace. That's the vendor's account of its own product, not an outside evaluation — treat the autonomy claim as a design goal.