Amazon Web Services on Monday enabled AI traffic monetization within AWS WAF, allowing sites behind Amazon CloudFront to charge AI agents in stablecoins per request through Coinbase’s x402 protocol. This is the first time a hyperscale cloud has connected on-chain payments directly to the content delivery edge.
This new feature is a first-party feature of AWS WAF Bot Control and is currently available to CloudFront customers at no additional charge, AWS announced in a news blog. Payment clearing and verification is done through Coinbase’s x402 Facilitator, allowing publishers to accept USDC on Base or Solana directly into their self-managed wallets. Support for Stripe and Machine Payments Protocol is coming soon.
When a Monetize rule matches an incoming request, AWS WAF returns an HTTP 402 Payment Required response with a JSON price manifest that includes the per-page price, authorized networks, destination wallet, and payment timeout. An x402-compatible agent runtime signs the payment and a facilitator validates it on-chain. Content is served within a single request cycle without new accounts, bills, or API keys.
This launch expands on the Coinbase-Amazon thread started in May with Bedrock AgentCore Payments connecting x402 to AWS on the agent side. CloudFront now closes the loop on the publisher side. The underlying protocol was spun out under the Linux Foundation in April, with AWS one of more than 20 founding members, and Coinbase CEO Brian Armstrong said last week that the platform has already processed more than 160 million autonomous x402 transactions in the past year.
“Agent traffic is growing exponentially and we are just getting started,” Nishit Sawhney, general manager of AWS Edge Services, said in a Coinbase post. “Now, with our partnership with Coinbase and x402, we can answer three questions before a single byte is delivered: Who is this agent? What is its intent? And does it have payment authority?” AWS WAF Bot Control powers over 650 AIs including GPTBot, Claude-Web, and Perplexity-Bot. We categorize bot and agent types and provide separate pricing for each validation tier.
Agent-native payment rails sit alongside the cloud console toggles that developers already use to configure cache and firewall rules. AWS said it does not process payments or receive a cut of content revenue. Payments are made through the publisher’s chosen wallet. Pricing, licensing terms, and chains other than Base and Solana are left up to the publisher, and neither company has disclosed launch customers or initial revenue figures.
