News
Coinbase CEO Says AI Agents Could Pay $0.25 Per Article, Ending Subscriptions
Coinbase CEO Brian Armstrong says stablecoins and the x402 protocol could replace monthly subscriptions with per-article micropayments handled by AI agents.
AI SummaryAI
- Brian Armstrong said stablecoins and x402 let businesses accept usage micropayments with less checkout friction.
- Armstrong argued an AI agent should pay publishers per article, using a $0.25 example price.
- Coinbase introduced the x402 protocol in May 2025, built on the HTTP 402 Payment Required code.
- In June Coinbase partnered with Amazon Web Services to monetize AI-agent requests through x402.
Armstrong's Case Against the Monthly Subscription
Coinbase CEO Brian Armstrong says stablecoins and the x402 payment protocol could dismantle the monthly subscription that still gates much of the web, replacing it with per-use micropayments. In a post on X, Armstrong wrote that stablecoins and x402 “enable businesses to accept micropayments for usage and decrease friction at checkout,” presenting the pairing as a way to cut payment friction for merchants and consumers alike. He was most explicit about online news: nobody, he argued, should have to buy a month-long subscription just to read a single article.
@brian_armstrong · X post
A post on X.
View on X
Under his model, an AI agent acting for the reader fetches the piece and settles with the publisher for that item alone, with no checkout step for the human. The example he used prices one newspaper article at $0.25: the agent receives a payment request from the publisher and, if the user has pre-authorized spending, returns a stablecoin authorization for the exact amount instead of hitting a paywall. Stablecoins are tokens pegged to a reference currency, which makes them the natural settlement asset for small, automated payments of this size. The protocol behind the pitch is not new. Coinbase introduced x402 in May 2025 as an open payment standard built on HTTP 402, the “Payment Required” status code that has existed since the internet's early days but was never widely used for money. The design goal is to turn that dormant status code into an automated settlement layer connecting websites, applications and AI agents, so a payment can travel with the request itself. For Coinbase, which operates trading, custody, payment and blockchain infrastructure, the pitch extends the company's ambitions from exchange services into payments rails.
AWS and Cloudflare Lay the x402 Rails
Armstrong's argument arrives while the plumbing for AI-driven payments is being assembled. In June, Coinbase worked with Amazon Web Services so that publishers running AWS CloudFront and the Web Application Firewall can route AI-agent requests into x402 revenue, meaning each machine request can carry a payment demand rather than being blocked. In September, Cloudflare put its own product into closed beta: the Monetization Gateway lets participating businesses bill AI agents for access to websites, datasets and application programming interfaces over the same protocol. Closed beta means the Cloudflare product is live for selected participants only, and no public rollout date has been given.
The two programs sit at different layers of the same stack:
| Company | Initiative | Scope |
|---|---|---|
| Coinbase | x402 protocol, May 2025 | Micropayments and AI payments |
| Amazon Web Services | Coinbase partnership, June | Monetizing publisher requests via x402 |
| Cloudflare | Monetization Gateway, September closed beta | Paid access to sites, datasets and APIs |
Coinbase Global, whose shares trade as COIN, is effectively asking the infrastructure industry to treat agent traffic as billable demand rather than cost. For publishers, the appeal is recapturing value from crawler traffic that currently consumes content for free.
The primary record here is Armstrong's own post, and it makes a product argument rather than an adoption claim: it names no publisher partners, no transaction counts and no revenue figures. That leaves the infrastructure as the verifiable part of the story. With AWS and Cloudflare both shipping x402 hooks, the rails exist before the demand, and the bottleneck is publisher opt-in. If per-request settlement scales, every paid fetch settles in stablecoins, which would give PayFi, the use of payment rails for real settlement flows, a consumer-facing case beyond trading. Watch for a Cloudflare beta-to-general-availability move and for publishers disclosing x402 revenue as the next confirmable data points.
Primary sources
AI-generated, AI-reviewed, under COINOTAG editorial oversight.

