Amazon Web Services on Monday turned on AI traffic monetization inside AWS WAF, letting any site behind Amazon CloudFront charge AI agents per request in stablecoins through Coinbase’s x402 protocol. It is the first time a hyperscale cloud has wired onchain settlement directly into its content-delivery edge.

The new capability is a first-party feature of AWS WAF Bot Control, available now at no extra charge for CloudFront customers, AWS announced on its news blog. Payment settlement and verification flow through Coinbase’s x402 Facilitator, with publishers able to accept USDC on Base or Solana directly to a self-managed wallet. Stripe and Machine Payments Protocol support are listed as coming soon.

When a Monetize rule matches an incoming request, AWS WAF returns an HTTP 402 Payment Required response carrying a JSON price manifest with the per-page price, accepted networks, destination wallet and payment timeout. Any x402-compatible agent runtime signs the payment, the Facilitator verifies it onchain, and the content is served inside a single request cycle, with no new accounts, invoices or API keys.

The launch extends a Coinbase-Amazon thread that started in May with Bedrock AgentCore Payments, which wired x402 into AWS on the agent side. CloudFront now closes the loop on the publisher side. The underlying protocol spun out under the Linux Foundation in April with AWS as one of more than 20 founding members, and Coinbase CEO Brian Armstrong said last week the platform has already processed more than 160 million autonomous x402 transactions over the past year.

“Agent traffic is growing exponentially, and we’re just getting started,” Nishit Sawhney, General Manager of AWS Edge Services, said in the Coinbase post. “Now, in partnership with Coinbase and x402, we can answer three questions before a single byte is served: who is this agent, what’s its intent, and is it authorized to pay.” AWS WAF Bot Control classifies more than 650 AI bot and agent types, including GPTBot, Claude-Web and Perplexity-Bot, with separate pricing for each verification tier.

Agent-native payment rails now sit alongside the cloud console toggles developers already use to configure caching and firewall rules. AWS said it does not process payments or take a cut of content revenue; disbursement runs through the publisher’s chosen wallet. Pricing tiers, license terms and any chains beyond Base and Solana are left to the publisher to configure, and neither company has disclosed launch customers or early-revenue figures.