How an old HTTP status code became the agent payment rail
The mechanical novelty of AgentCore Payments is small but consequential: instead of inventing a new payment API, AWS standardized on x402, which uses the HTTP 402 'Payment Required' status code that has sat unused in the HTTP spec since the early web. When an agent requests a paid resource, the server replies with a 402 response and a payment specification — chain, asset, amount, recipient — and the agent's wallet signs and submits the payment before retrying the request. Per the AWS industry blog, 'when an agent requests a resource or service, the server responds with a status 402 response and a payment specification.'
The consequence is that any HTTP server — an API, an MCP server, a paywalled web page, even another agent — can demand a stablecoin micropayment without onboarding to a custom payment SDK. AWS's choice to bake this into AgentCore rather than build a proprietary scheme is what makes it interoperable with Cloudflare's Agents SDK and Google's AP2, both of which target x402. That is the structural shift: payments become a property of the web, not of a vendor.




