Coinbase and AWS let publishers accept agents as customers via x402
TL;DR: Coinbase is working with AWS CloudFront and WAF to let the web publishers and API providers behind a quarter of the internet accept agents as customers via x402.

Roughly a quarter of the internet runs on AWS CloudFront and Web Application Firewall. Starting today, that quarter of the internet can now accept payments from AI agents —a toggle-on solution powered by x402 and Coinbase's x402 Facilitator, enabled from their existing AWS configuration.
AI agents are increasingly becoming autonomous actors on the internet: browsing content, querying APIs, analyzing data, and taking actions on behalf of users. But today most publishers either block AI traffic outright or give away their content for free.
Now, website publishers, API providers, and digital services can treat AI agents as a new class of paying customer. With AWS and Coinbase, they can start earning from the agent traffic that's already hitting their endpoints.
From request to revenue, in one cycle
Publishers on CloudFront and WAF can enable AI traffic monetization directly from their existing AWS configuration. When an AI agent requests content, it gets back an HTTP 402 with exactly what to pay and how. It pays. Coinbase's x402 Facilitator verifies it. Content is served. All in one request.
‘HTTP 402 Payment Required’ has existed as a status code since the earliest days of the web. It was always intended as a way for servers to require payment before serving content. Until now, it was never fully realized. x402 changes that.
x402 is payment method agnostic. USDC on Base is the natural starting point — fast, cheap, and widely used — but the protocol does also support other digital assets, blockchains, and is built to accommodate fiat rails as the ecosystem grows.
x402 also supports multiple payment schemes beyond simple per-request charges. Developers can implement batch settlement for high-frequency micropayments, subscription models for repeat-access agents, and variable-rate pricing for usage-based workloads like inference or compute-heavy API calls. This gives content owners and publishers the flexibility to price their content in whatever way reflects its value, and gives agent developers the ability to optimize for cost and reliability across different use cases.
With no new accounts, invoices, or API keys, x402 is designed as a simple, modern payments protocol.
“Agent traffic is growing exponentially, and we’re just getting started. Content owners and publishers want to enable their users and their agents, not block them. Earlier this year we launched AI identification with Web Bot Authentication. 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. That changes the conversation from defence to commerce.”
— Nishit Sawhney, General Manager, AWS Edge Services
"We started x402 so the internet could have a native payment layer for agents, as they become one of the largest sources of web activity. Until now, publishers had no way to capture value from this new and growing customer segment. Integrating x402 into AWS CloudFront and WAF means any publisher can start earning from that growing activity today — with no new infrastructure or negotiations."
— Brian Foster, Head of Infrastructure Growth, Coinbase
An open protocol, built for the whole ecosystem
The x402 protocol powering this integration is an open standard. Coinbase incubated x402 and has since spun it out as an independent Foundation under the Linux Foundation. AWS is among the founding members, alongside more than 20 major technology companies across cloud infrastructure, AI, and financial services.
Like HTTP itself, x402 is a neutral and open protocol that anyone can implement, build on, or extend. Its governance under the Linux Foundation ensures it remains that way. That openness is precisely what makes broad, rapid adoption possible: no single company controls the standard, which means the entire ecosystem can freely innovate on top of it.
Discovery: x402 Bazaar and Agentic Market
In order for agents to pay for content, they first need to find it. The x402 Bazaar is an open, searchable registry of x402-enabled endpoints, giving agents and developers visibility into what services are available, at what price, and with what capabilities. Publishers enabling AI traffic monetization through CloudFront can make their endpoints discoverable in the Bazaar, opening them to the full global ecosystem of AI agents.
For users, developers and enterprises that want a vetted, curated set of high-quality services, Coinbase also operates the Agentic.Market: a curated catalog of reliable x402 services built for agentic workflows.
Build for enterprises: Security and compliance at the settlement layer
Coinbase's x402 Facilitator handles onchain verification and settlement for every payment processed through this integration. It is built for the reliability and security that AWS enterprise customers require: high availability, onchain USDC settlement across top blockchain networks, and built-in compliance screening on every transaction.
A new revenue model for the open web
The web has always been built around the assumption that its users are human. AI agents are changing that assumption fast. This launch gives a meaningful portion of the web's infrastructure a way to serve both, with a payment model native to how agents operate: autonomous, programmable, and settled instantly.
Get started
Learn more about AI traffic monetization in CloudFront and WAF: https://aws.amazon.com/blogs/aws/aws-waf-adds-ai-traffic-monetization-capability-to-help-content-owners-charge-ai-bots-for-content-access/
Learn more about Coinbase's x402 Facilitator and agentic payment infrastructure: https://docs.cdp.coinbase.com/x402/welcome
Explore x402-enabled services: https://agentic.market/
Learn about the x402 Foundation: https://www.linuxfoundation.org/x402foundation




