AWS WAF lets publishers charge AI bots for content

AWS has added an AI traffic monetisation feature to AWS WAF, allowing publishers and other content owners to charge AI bots for access to web content.

The addition extends AWS WAF Bot Control, which already lets customers identify, block and limit automated traffic. The new feature adds pricing rules and payment collection for AI agents at the network edge. Support is currently limited to web access control lists linked to Amazon CloudFront distributions.

Content owners can set per-request charges by content path, bot category or verification tier without changing origin infrastructure or adding application code. They can also define access policies for different agent types, receive stablecoin payments to a chosen wallet and track bot activity and revenue through a dashboard.

The launch addresses growing tension between publishers and AI companies over the use of online material. According to AWS, AI bot traffic now accounts for more than half of web traffic for many content providers, while AI-specific crawlers have risen by more than 300% year-on-year.

That traffic can impose bandwidth and infrastructure costs on publishers without delivering the referral traffic, advertising impressions or subscription conversions that often accompany traditional search indexing. Unlike search engine crawlers, AI bots may use content to generate summaries and responses in AI interfaces without directing users back to the source.

How it works

Under the new system, AWS WAF can return an HTTP 402 Payment Required response when a monetised rule matches an incoming request. The response includes a machine-readable price manifest in JSON format using the x402 protocol for machine-to-machine payments.

The manifest can include the content price in USDC, accepted blockchain networks, the destination wallet address, a payment timeout and the payment scheme. An x402-compatible agent runtime can then submit a signed payment authorisation. The service verifies the request, retrieves the content and works with third-party facilitator services to settle the payment on-chain before serving the response.

Payment settlement and verification are currently provided through Coinbase's x402 Facilitator. Support for direct account payments through Stripe and compatibility with the Machine Payments Protocol are due to be added later.

Customers can assign one of six actions to each agent verification tier in a protection pack: Monetise, Allow, Block, Count, CAPTCHA or Challenge. They can also create multiple protection packs for different content zones within the same distribution, allowing different pricing and access terms for separate sections of a site.

AWS WAF Bot Control classifies more than 650 AI bots and agent types, including GPTBot, Claude-Web and Perplexity-Bot. It groups them into verified and unverified tiers, with verified agents identified through cryptographic signatures or documented IP ranges and unverified agents recognised through user-agent matching, behavioural fingerprinting and IP reputation signals.

Dashboard view

Before setting charges, customers can review an AI traffic analysis dashboard that breaks requests into four categories: all bot requests, AI bot requests, verified AI bot traffic and unverified AI bot traffic. The dashboard also shows infrastructure impact metrics such as bandwidth consumed, estimated monthly cost and peak request rates, along with a per-path heatmap of bot activity.

Once real payments are enabled, a separate AI access monetisation dashboard tracks total revenue, average revenue per request and the split between verified and unverified bots. It also groups earnings by bot category and ranks content paths by revenue generated, while a settlements tab shows the distribution of payment methods and failed payment attempts.

The service includes a test mode that mirrors the production payment flow on test networks. Users can switch between test and real currency modes in the monetisation settings, with test transactions logged separately and excluded from the live revenue dashboard.

Stripe role

Stripe said it will provide payment infrastructure for the AWS WAF feature through an upcoming integration that would let content owners receive funds directly into bank accounts. That would expand payment options beyond wallet-based stablecoin settlement.

Kevin Miller, Head of Payments at Stripe, described the broader commercial backdrop for the service.

"Agents are rapidly growing as content consumers on the internet: reading text, calling APIs, and querying databases. This presents new opportunities for businesses to monetise their valuable content and data while empowering agents to make more informed decisions," said Miller. "With Stripe and the Machine Payments Protocol powering AI traffic monetization, businesses can now quickly monetize their content, data, and APIs."

AWS framed the move as part of a broader push towards common payment standards for automated agents.

"For agent payments to scale, they need standards for interoperability, the same way the web needed HTTP. We will be integrating Stripe into AWS WAF AI traffic monetisation so any agent can pay, and any publisher can get paid, without custom integrations on either side," said Anoop Dawani, Director of Product Management at AWS Network Services.

AWS said the AI traffic monetisation feature is available to Amazon CloudFront customers at no extra charge beyond standard AWS WAF pricing, across edge locations where AWS WAF web ACLs are associated with CloudFront distributions.