Is Your Site Ready to Sell to AI Agents? x402 and Machine-Readable Pricing

In our post on the Cloudflare Wallets announcement we covered how AI agents are starting to acquire identities and wallets. This post is the other side of the coin: while buyers become agents, is the seller side — your site, your content, your API — ready for them?

The question may sound futuristic, but the groundwork is being laid today: more than half of web traffic already comes from bots, AI tools do a growing share of shopping research on users’ behalf, and the payment layer is standardizing around x402. Preparation happens while competitors are unprepared — not after demand explodes.

This post is part of the AI Visibility Guide; see the guide for all four layers.

x402 in One Minute

x402 is an open protocol built on the HTTP status code 402 Payment Required that attaches payment to an HTTP request. The flow is simple: the agent requests a paid resource, the server replies with 402 and a price, the agent pays if its wallet policy allows, retries the request, and receives the response. No subscription, no signup form; per-request selling. The protocol is developed by a consortium led by Coinbase, with Cloudflare and Stripe participating.

The business-model meaning is this: things you cannot sell at all today because “a subscription isn’t worth it” — a single report, a single data query, a single content page — become sellable at a unit price of a few cents.

Who Is This an Opportunity For?

• API owners: Currency, stock, pricing, logistics data… Agents can trial dozens of APIs with small payments to find the best source; the service without a signup barrier is the service that gets compared.
• Content producers: A third path opens between blocking bots entirely and giving content away: charging per request.
• E-commerce: Stores that expose product data in a form agents can read and compare will enter the new storefront called “agent recommendation”; those that don’t will simply not appear in it.

The Readiness Checklist

Order matters — visibility first, payment second:

1. A machine-readable foundation: Structured data (schema.org) on product and service pages, a consistent heading hierarchy, agent entry points like llms.txt. An agent that cannot understand you cannot pay you either. This layer is also exactly today’s technical SEO — the investment pays back immediately.
2. Your API’s contract: An OpenAPI definition, predictable error behavior, rate limiting. A human developer reads the docs and tolerates gaps; an agent cannot.
3. The unit-price decision: What would you sell per request? The price list must be machine-readable; the x402 challenge already carries the price in the response.
4. Recognizing agent identities: Telling which agent acts on whose behalf (e.g. cloudflare.pay handles) will be the new way to separate good agents from bad bots.
5. An MCP surface: Exposing your service as a tool agents can call means securing shelf space in the “agent store”.

A Realistic Timeline

Let’s be honest: x402 payments are early-stage today, and Cloudflare Wallets’ payment features have not opened yet. This post’s advice is not to expect revenue tomorrow — it is to do steps 1 and 2 now, since their cost is low anyway, and to roll out 3–5 together with the ecosystem. The first two steps pay back as SEO and integration quality even if agents never show up; if they do, you are ready.

If you would like to review your API or product data against this checklist, take a look at our API development and integration service, or write to us.