Amazon Web Services has rolled out AI traffic monetization across CloudFront and AWS WAF. Coinbase’s x402 protocol powers the new capability. As a result, websites and APIs running behind AWS edge infrastructure can now charge AI agents directly for access. Payments settle on-chain in USDC. The feature went live on June 15, 2026, according to the official AWS announcement.
Publishers and API providers can turn this on from their existing CloudFront config today.
— Coinbase Developer Platform🛡️ (@CoinbaseDev) June 15, 2026
The result: a new revenue stream, where you can charge AI agents for content and API access instead of blocking that traffic or serving it for free.
Learn more: https://t.co/e7MnbRLp0w
What AWS Actually Shipped
The new feature lives inside AWS WAF Bot Control as a “Monetize” rule. Content owners configure pricing directly in the AWS WAF console. When an AI agent hits a protected endpoint, AWS WAF returns an HTTP 402 “Payment Required” response. That response carries a machine-readable JSON price manifest. The manifest follows the x402 open protocol for machine-to-machine payments.
Inside the manifest, the agent sees the price in USDC and the accepted blockchains. Currently, the system supports Base and Solana for stablecoin settlement. Additionally, the manifest includes the destination wallet address, payment timeout, and payment scheme. Coinbase’s x402 Facilitator handles settlement and verification on-chain. Importantly, AWS confirmed the feature carries no extra charge beyond standard AWS WAF pricing.
How the x402 Handshake Works
The protocol revives HTTP 402, a status code that sat unused in the HTTP specification for decades. Coinbase launched x402 in May 2025 as a new standard for internet-native payments, per its developer platform launch page. The flow is simple. First, the AI agent requests a resource. Next, the server replies with a 402 status and payment terms in the response body. Then the agent signs a USDC payment authorization and retries the request with an X-PAYMENT header.
After that, the x402 Facilitator validates the payment and settles it on-chain. Finally, the server returns the requested data along with a confirmation header. Settlement on Base takes roughly 200 milliseconds. Furthermore, transaction fees stay below one cent, making per-request micropayments economically viable for the first time. No accounts, subscriptions, or checkout flows are required at any step.
Why AI Agents Need This
Traditional payment rails were designed for human checkout, not machine-to-machine billing. Subscriptions, API keys, and credit card forms break down when an autonomous agent needs to pay a few cents for a single query. Meanwhile, AI agents now consume enormous volumes of web content for training, research, and real-time tasks. Publishers have struggled to monetize that traffic or even distinguish it from human visitors. As a result, content owners have asked for a way to charge bots without blocking them entirely.
The x402 integration solves that problem at the network edge. Notably, agents pay per page, per query, or per API call in the same HTTP request. Publishers receive USDC directly into a wallet of their choice. AWS handles the infrastructure, while Coinbase handles the wallet, compliance, and settlement layer. Consequently, both sides plug into a shared standard without building custom billing systems.
CloudFront, WAF, and Lambda@Edge Together
AWS designed the integration to live entirely at the edge. The Monetize action runs inside web ACLs attached to Amazon CloudFront distributions. Additionally, Lambda@Edge can extend the logic for custom pricing or content gating. The x402 handshake completes between the agent and the edge, never touching origin infrastructure. AWS describes CloudFront and WAF as the backbone for roughly a quarter of the internet.
That footprint matters because adoption hinges on reach. Any site already fronted by CloudFront can adopt x402 with a console change rather than a code rewrite. Sample implementations live in public AWS GitHub repositories, giving developers working templates. Furthermore, the integration builds on Amazon Bedrock AgentCore Payments, which Coinbase and AWS launched together in May 2026. AgentCore already routes agent payments through the x402 Facilitator and Coinbase’s wallet infrastructure, as detailed in the Coinbase announcement.
The Numbers Behind x402
Adoption has moved quickly in x402’s first year on the market. The protocol has processed more than 169 million payments to date. Over 590,000 buyers and 100,000 sellers have transacted through x402-enabled endpoints. Membership in the x402 Foundation now includes AWS, Coinbase, Anthropic, Circle, NEAR, and dozens of other companies. The standard remains open and chain-agnostic, though Base and USDC dominate early deployments.
Coinbase has also indexed a growing catalog of agent-accessible services. Examples include Exa for search, Messari for market data, and Browserbase for browser automation. These services give agents real, paid access to premium tooling on a per-call basis. As a result, agent builders can chain commercial APIs together without negotiating separate contracts for each one.
What Comes Next
AWS confirmed that Stripe integration and Machine Payments Protocol support are on the near-term roadmap. That addition would let publishers accept traditional card-based payments alongside on-chain stablecoin settlement. Furthermore, AWS WAF Bot Control already differentiates AI bot traffic from human users, giving publishers fine-grained control over who pays what. The combination of identification and monetization creates a complete pricing layer for agent traffic.
For the broader market, the announcement signals that hyperscalers see agent commerce as a real revenue category. Coinbase, meanwhile, has positioned itself as the default settlement layer for that economy. The x402 standard remains open, so competing facilitators can enter the market. However, the AWS partnership gives Coinbase a sizable head start on distribution. Genfinity will continue tracking adoption as more CloudFront customers turn the feature on.
*Disclaimer: News content provided by Genfinity is intended solely for informational purposes. While we strive to deliver accurate and up-to-date information, we do not offer financial or legal advice of any kind. Readers are encouraged to conduct their own research and consult with qualified professionals before making any financial or legal decisions. Genfinity disclaims any responsibility for actions taken based on the information presented in our articles. Our commitment is to share knowledge, foster discussion, and contribute to a better understanding of the topics covered in our articles. We advise our readers to exercise caution and diligence when seeking information or making decisions based on the content we provide.
