Coinbase and Amazon Web Services are letting publishers running on AWS CloudFront and Web Application Firewall charge AI agents for content access through the x402 protocol, the two companies announced Monday. The integration sits on infrastructure AWS says powers roughly a quarter of the internet, and publishers can toggle it on inside their existing AWS configuration — no new accounts, invoices, or API keys required.
When an AI agent requests a resource, the server returns an HTTP 402 "Payment Required" response with a price. The agent then settles in USDC on Base, Coinbase's x402 Facilitator verifies the payment onchain, and the content is served — all inside a single request cycle. The setup supports per-request charges, batch settlement for high-frequency micropayments, subscription pricing, and variable-rate models for inference or other compute-heavy workloads.
Why it matters
"Content owners and publishers want to enable their users and their agents, not block them," said Nishit Sawhney, general manager of AWS Edge Services, framing the integration as a way to identify an agent's intent and payment authorization before any content is served. Coinbase incubated x402 before spinning governance out to the x402 Foundation under the Linux Foundation, with AWS among more than 20 founding members spanning cloud infrastructure, AI, and financial services.
The distribution surface is the point: x402 already had Stripe integration for USDC billing, a v2 multi-chain upgrade in December, and the Agentic.Market launch in April. Layering it onto CloudFront turns the protocol from a developer experiment into a default option for the millions of sites already fronted by AWS.
Market impact
Publishers can list endpoints on the open x402 Bazaar registry or on Coinbase's curated Agentic.Market. Coinbase separately rolled out dedicated agent accounts under its "Coinbase for Agents" product earlier this month, with more than 10,000 merchants already integrated into the protocol.
Frequently asked questions
-
What is the x402 protocol that Coinbase and AWS are integrating?
x402 is an open payments protocol incubated by Coinbase and now governed by the x402 Foundation under the Linux Foundation. It uses the HTTP 402 "Payment Required" status code to let clients, including AI agents, pay for resources on a per-request basis — typically in USDC on Base.
-
How do publishers enable x402 billing on AWS CloudFront?
Publishers can toggle the feature on inside their existing AWS CloudFront and WAF configuration. The integration requires no new accounts, invoices, or API keys — when an AI agent requests content, the server returns a 402 with a price, the agent pays in USDC on Base, and Coinbase's x402 Facilitator verifies the…
-
Which AWS services does the x402 integration cover?
The integration covers AWS CloudFront, the content delivery network, and AWS Web Application Firewall (WAF). AWS says CloudFront and related edge services power infrastructure that handles roughly a quarter of the internet.
-
What pricing models does the x402 integration support?
The integration supports per-request charges, batch settlement for high-frequency micropayments, subscription models, and variable-rate pricing for usage-based workloads such as inference or compute-heavy API calls.
-
How many merchants are already on x402 and what comes next?
Coinbase said more than 10,000 merchants are already integrated into the x402 protocol as of its "Coinbase for Agents" launch earlier this month. Publishers can list endpoints on the open x402 Bazaar registry or on Coinbase's curated Agentic.Market to start receiving agent payments.
TheBlock