Monetize AI Agent API: Per-Request Pricing with x402

If you operate an API, AI agents are a customer segment your billing system was never designed for. An agent cannot complete your signup flow, will not commit to a monthly plan, and makes purchase decisions in milliseconds. x402 lets you sell to this segment directly: declare a price per call, let a facilitator handle settlement, and get paid in USDC the moment your response is delivered. This guide covers how builders are pricing agent traffic, how to choose a chain and a facilitator, and how to set a price point that agents will actually pay.

Why per-request pricing fits agent buyers

Agents consume APIs opportunistically. A research agent might call a search endpoint fifty times in an hour and then never again; a trading agent might poll a price feed around the clock but refuse anything above a strict per-call budget. Subscriptions fail both of them: the light buyer will not sign up, and the heavy buyer is mispriced. Per-request pricing matches revenue to usage exactly, with no invoicing cycle, no dunning, and no plan tiers to maintain.

The directory data bears this out. All 100 services indexed by x402 Looker charge per request — it is the only pricing model in the catalog. Prices are declared inside each 402 response, so you can price different endpoints differently, change a price without a billing migration, and let the market see your offer in a machine-readable form.

What the directory shows about pricing

Listed prices in the directory span five orders of magnitude, from $0.00001 to $10 per request. They cluster into four bands, each of which has its own page:

• Micro — $0.01 or less per request: the largest band, with 32 listings. Commodity data calls and lightweight lookups live here.
• Low — over $0.01 up to $0.10: 9 listings, mostly richer data queries.
• Moderate — over $0.10 up to $1.00: 30 listings, heavily weighted toward market data and analytics.
• Premium — over $1.00 per request: 28 listings, dominated by high-value finance and trading endpoints.

The pattern is intuitive: the more expensive the underlying data or computation, and the more directly the output feeds a revenue-generating decision, the higher the per-call price a buyer tolerates.

Choosing a chain

x402 payments in this directory settle in USDC on one of two networks. Base, an Ethereum layer-2, hosts 87 of the 100 listings and is where the majority of agent wallets hold their USDC. Solana hosts the remaining 13 and offers high throughput with low transaction costs. The practical question is not which chain you prefer but which chain your buyers' wallets already hold USDC on — an agent will simply skip an endpoint it cannot pay. Check which facilitators support your chosen network before committing.

Choosing a facilitator

A facilitator verifies each signed payment and settles it on-chain, so you never run nodes, manage RPC access, or watch for confirmations. Seven facilitators settle the listings in this directory, and adoption varies widely:

• coinbase — 83 listings, the dominant operator and the one behind the protocol itself.
• payai — 5 listings, active on both Base and Solana.
• codenut — 5 listings, all on Base.
• dexter — 4 listings, all on Solana.
• corbits, daydreams, and mogami — one listing each.

Evaluate candidates on chain coverage, the quality of their verification and settlement API, their documentation, and how much of the ecosystem already routes through them. Adoption matters because it proxies for reliability and for how many client libraries already speak to that facilitator.

Setting a realistic price point

Start from unit cost. Add up what one call actually costs you — compute, upstream data licenses, bandwidth — and apply a margin. Then sanity-check the result against the band your category lives in: if comparable endpoints price in the micro band and you are quoting fifty cents, agents will route around you, because switching providers at the protocol level costs a buyer nothing. If your output is genuinely differentiated — proprietary signals, expensive generation, scarce data — the premium band shows buyers will pay more than a dollar for a single call. When in doubt, price low and raise: every request you lose to price is invisible, but every request you win is data.

Getting discovered

A paid endpoint no one can find earns nothing. Agents and the humans who configure them discover services through directories and through agent-native interfaces, so list your service where buyers look and, where it fits, expose it as an MCP tool so agent frameworks can call it directly.

Ready to sell to agents? Submit your x402 service to the directory, and study the facilitator profiles to pick your settlement partner.