AWS has added a pay-per-crawl pricing layer directly inside its Web Application Firewall, giving content publishers the ability to charge AI bots for each page they consume rather than block them outright or absorb the cost of free access. The feature, called AI traffic monetization, shipped on June 15 and is available at no extra charge on top of standard AWS WAF pricing for CloudFront customers.
The practical mechanics are more specific than most infrastructure announcements. Publishers configure “protection packs” through the AWS WAF console that define pricing rules by content path, by bot category, and by verification tier. No origin code changes required; no custom payment infrastructure to build. When a monetized request arrives, WAF returns an HTTP 402 Payment Required response containing a machine-readable JSON price manifest via the x402 protocol. An x402-compatible agent runtime can then submit payment autonomously on Base or Solana in USDC, after which WAF clears the request and serves the content. AWS takes no fee on the revenue; disbursement goes directly to the publisher’s wallet.
The classification layer underneath this matters. AWS WAF Bot Control already identifies more than 650 distinct AI bot and agent types, including GPTBot, Claude-Web, and Perplexity-Bot. The system splits them into two tiers: Verified (identity confirmed via Web Bot Auth Ed25519 signature or documented IP ranges) and Unverified (recognized by behavioral fingerprinting and user-agent matching but not cryptographically confirmed). Publishers can price these tiers differently, block one while charging the other, or allow some agents free access while metering others. The payment settlement layer is currently provided by Coinbase’s x402 Facilitator, with Stripe and Machine Payments Protocol support listed as coming soon.
The context AWS provides is worth taking at face value. AI bot traffic now accounts for more than 50 percent of web traffic at many content properties, with AI-specific crawlers up more than 300 percent year over year. Unlike traditional search crawlers, which send referral traffic back to publisher sites, AI crawlers consume content to generate summaries and answers delivered inside AI interfaces. Publishers carry the infrastructure cost with no page views, no ad impressions, and no subscription conversions to offset it.
This is the infrastructure layer the “pay-per-crawl” economy has been waiting for. Until now, publishers had two options: block AI bots via robots.txt (which bots can ignore) or negotiate individual licensing agreements (which requires resources most publishers do not have). AWS is offering a third path: automated micropayment metering at the network edge, enforced before a request reaches the origin server.
The open question is whether AI companies will pay rather than route around it. An agent that encounters a 402 and lacks an x402 payment runtime will simply fail to retrieve the content. Labs that have invested in x402 compatibility will pay; those that have not will hit a wall. Nothing in the AWS announcement compels any AI company to implement x402 support, and the system cannot extract payment from a bot that refuses to complete the flow. Publishers setting aggressive prices risk shrinking their AI-driven reach entirely, while those setting prices too low may simply subsidize the same extraction at a new fixed rate.
For publishers running content on CloudFront, the more immediate decision is about configuration, not strategy: the AI traffic analysis dashboard surfaces per-path bot activity heatmaps and infrastructure cost metrics before you set a single price. That data alone, available now at no additional cost, is worth activating.
Publishers building on CloudFront should enable Bot Control at Common or Targeted level and activate the AI traffic analysis dashboard this week to establish a baseline before committing to any pricing strategy.
AWS announced AI traffic monetization for AWS WAF on June 15, 2026, in a post on the AWS News Blog.
