Two years ago, "can we even charge AI agents?" was an open question. In 2026 it isn't — the question is which way fits the traffic you actually have. Below are five concrete ways to turn machine traffic into revenue, what each is best for, and where the honest trade-offs are. Most teams use one or two of these, not all five.
1. Charge AI crawlers at the edge
If you run a content site, the fastest path doesn't touch your code at all. You connect Cloudflare, and a Worker decides — at the edge, before the request reaches your origin — whether to allow, block, or charge each request. AI crawlers get a price instead of free content; human visitors pass through untouched.
- Best for: publishers and content sites whose pages are being scraped for free.
- Why it works: you stop choosing between "block and lose reach" or "allow and earn nothing." The same traffic becomes a stream of small payments.
- Setup cost: near zero — no origin or code changes.
See charging AI crawlers for your content.
2. Charge per API call with a drop-in SDK
If you sell an API, meter the routes worth metering and let agents pay per call. You register a route and price, add one middleware, and that endpoint returns a signed x402 challenge; the agent pays in USDC and the call succeeds.
- Best for: APIs whose callers are autonomous and often one-off — they won't sign up for a plan.
- Why it works: no key or plan to provision for callers you'll never meet. Payment happens in the request.
- Setup cost: a few lines — nine official SDKs across the common stacks.
See the full walkthrough in the API monetization playbook and pay-per-call in the glossary.
3. Charge per tool call on an MCP server
If you expose tools to agents through MCP, you can put a price on each tool call. MCP standardizes how an agent discovers and calls your tool; x402 standardizes how it pays. You expose the price; the agent's runtime funds the payment and attaches proof on retry — you don't handle the wallet.
- Best for: MCP server authors with genuinely useful tools.
- Why it works: you monetize individual invocations without inventing a billing system or touching crypto.
- Setup cost: register each tool's route and price; start in test mode.
4. Charge per query on data & RAG endpoints
High-value data is exactly what agents want to call repeatedly — search, embeddings, retrieval. Put a per-query price on those endpoints and you charge in proportion to actual use, without negotiating a contract for every caller.
- Best for: data providers and AI-infra teams whose endpoints are high-value and high-frequency.
- Why it works: scraping-for-free becomes pay-per-query; you price each endpoint to match its cost and value.
- Setup cost: same one-middleware integration as any API route.
See charging for data & RAG endpoints.
5. The familiar alternatives — and when they still win
Pay-per-call isn't the only option, and it isn't always the right one. Two established approaches still have their place, and pretending otherwise would be dishonest:
- API keys + metered billing. Provision a key, meter usage, invoice monthly. Still the right call for known customers on contracts. It struggles only when the caller is an agent that won't sign up first. (Paywall vs API keys.)
- Card-rail / agentic payments (e.g. Stripe). Mature, global, with chargebacks and dispute handling — the better fit for consumer-facing flows and high-frequency in-session billing. (Paywall vs Stripe.)
The honest summary: if your callers are autonomous and sporadic, per-call in USDC is the lighter substrate; if they're known businesses on monthly contracts or consumers who need chargebacks, the alternatives fit better. The full breakdown — including L402 on Lightning — is on the comparison hub.
How to choose
Don't agonize over the menu. Pick based on what you run:
| If you run… | Start with |
|---|---|
| A content site | Edge paywall for crawlers (#1) |
| A general API | Pay-per-call SDK (#2) |
| An MCP server | Per-tool pricing (#3) |
| A data / RAG service | Per-query pricing (#4) |
| A product for known, contracted customers | Keep API keys; add per-call for agents |
All four of the pay-per-call paths share the same foundation: the open x402 protocol (governed under the Linux Foundation since April 2026), priced in USDC, with a free test mode so you can prove the loop before any real money moves.
Next steps
- Browse the use cases: ways to get paid by machines
- Compare the approaches honestly: the comparison hub
- Learn the vocabulary: the x402 glossary
- Check the cost: pricing — free to start, no card
- Try it: create an account