AWS prices agent requests with x402

AWS now documents an AI traffic monetization mechanism in WAF built on x402, an open protocol for machine-to-machine payments. The central fact is straightforward: a website or API protected by AWS WAF in front of a CloudFront distribution can respond to an agent with an HTTP 402 “Payment Required” status containing a price in USDC, the accepted networks (Base and Solana), a payment address, and the parameters needed for authorization. If the agent pays correctly, AWS WAF verifies the payment and allows the request through to the content.

This infrastructure detail matters because it moves the agent-commerce discussion from a broad idea to a very concrete primitive: how a machine can pay for a web resource without a form, a customer account, or a credit card. HTTP 402 has existed for a long time as a payment-related status code, but it has mostly remained theoretical. x402 gives it a software-readable format. In the lifecycle described by AWS, the client requests a page, an article, a data feed, or an API. If a WAF rule with the “Monetize” action matches, the request receives a 402 response. The agent then signs a payment authorization with its wallet, or through a server wallet API, and retries the request with a payment header.

The blockchain layer is not cosmetic. AWS says settlement happens in USDC through Coinbase Developer Platform’s x402 facilitator service, after synchronous verification in the request path. Put simply, content is served only after confirmed payment. AWS also describes two useful protections: if the origin returns a 4xx or 5xx error, settlement is skipped and the client is not charged; and the protocol can avoid duplicate payments on some retries through a payment identifier that remains usable for up to 15 minutes. That shows the problem is not only making agents pay, but making them pay without breaking basic web behavior such as retries and application errors.

For publishers and API providers, this offers a third path between blocking bots and leaving all access free. They can set per-request pricing for resources served through CloudFront, including web pages, articles, endpoints, structured datasets, and media assets. For blockchain, the broader signal is important. Stablecoins are no longer framed only as money moving between people or companies. They are becoming a possible settlement layer for very small software calls, where the amount may be too low or too frequent for conventional payment rails. Adoption is still an open question: agents must implement the headers, publishers must price access sensibly, and users will need spending controls. But putting x402 inside WAF gives the protocol a serious foothold at the layer where much of web traffic is already filtered.