On June 18, Solana announced on X that AWS (Amazon Web Services) has launched an AWS WAF AI monetization system, allowing publishers delivering content via Amazon CloudFront to charge USDC per request to AI bots and agent programs. Payments can be settled on Solana or Base via the x402 protocol.
HTTP 402 Responses and x402 Payment Flow for AWS WAF AI Traffic Monetization
According to the AWS announcement, the complete flow for AI agent requests to pay for content is as follows: when an unauthorized AI agent requests paid content, AWS WAF returns an HTTP 402 Payment Required response, which includes the price, supported blockchain network, and the publisher’s wallet address. An x402-compatible agent program signs the payment authorization and resubmits the request. The x402 settlement process verifies the payment status before the content is published. If the publisher’s server returns an error, the transaction is not settled, and the agent program is not charged.
This mechanism replaces the dilemma publishers have previously faced, having to choose between “free scraping” and “complete blocking.”
Identification Coverage and Pricing Rules for AWS WAF Bot Control
AWS WAF Bot Control can identify more than 650 types of AI bots and agent programs. Publishers can set differentiated rules for individual requests:
· Verified crawlers can access for free
· Unverified agent programs can be assigned higher fee rates
· Certain content can be set to be completely blocked
Publishers can track the number of paid requests, average revenue, bot categories, settlement failures, and the content paths with the highest earnings—directly assessing whether AI traffic covers its infrastructure and licensing costs.
Coinbase’s Role as an x402 Service Provider and Its Fee Structure
Coinbase handles payment verification and blockchain settlement, so publishers don’t need to operate on-chain infrastructure themselves in order to accept machine payments. AWS holds no funds and does not take any share from content revenue. USDC is transferred directly from the wallet controlled by the agent program to the publisher.
This integration is a continuation of Solana’s strategy in the self-custody business domain: the Solana network previously rolled out a developer toolkit for AI agents and x402 payments; Coinbase has also connected x402 to AI assistants capable of completing transactions from users’ accounts.
Frequently Asked Questions
How is the x402 protocol different from existing subscription or advertising models?
According to the AWS announcement, the key difference of the x402 protocol is “pay per request”: publishers don’t need to set up accounts, invoices, or recurring payment agreements—USDC settles directly after each AI agent request for eligible content. Subscription models target human users, and advertising models rely on browser traffic, while AI agent access behavior does not fit either of these traditional monetization paths.
Do publishers need to build their own blockchain infrastructure?
No. According to the AWS announcement, Coinbase, as the x402 service provider, is responsible for payment verification and blockchain settlement. Publishers don’t need to run their own on-chain infrastructure; they only need to specify a wallet address to receive USDC.
Is this feature currently available to all AWS customers?
According to the AWS announcement, this feature currently applies to “AWS WAF customers protecting Amazon CloudFront,” and not all AWS service users can use it. It requires delivering content via Amazon CloudFront and having AWS WAF deployed.
