State of x402 pricing in 2026: what agents actually pay
A practical reading of visible per-call prices in the TOLL·402 catalog, including what the data can and cannot support.
DIRECT ANSWER
x402 prices cluster around fractions of a cent to a few cents per call, but public price coverage is still incomplete. In the curated TOLL·402 seed, fewer than all listings expose a concrete minimum price. Buyers should compare the quoted 402 requirement at call time, set a spend cap, and treat directory prices as a dated reference rather than a guarantee.
Key takeaways
- A visible directory price is useful for comparison, but the server's current 402 requirement is authoritative.
- Unknown pricing should remain unknown; converting missing data to zero makes free and unverified look identical.
- Agent budgets need per-call caps and workflow-level limits because a cheap request can still loop thousands of times.
What the directory can measure
TOLL·402 stores provider, tool, network, minimum and maximum USD price, quote-check date, and verification state separately. That permits honest counts and price-band comparisons without pretending every service has the same billing unit. A web-search call, an image generation job, and a gateway request may all be priced per call while delivering very different amounts of work.
- Use minimum and maximum prices only when the endpoint or provider states them.
- Keep free tools distinct from tools whose price varies or is missing.
- Show the observation date beside any ecosystem-wide price claim.
How buyers should interpret a price
The current x402 buyer flow starts with an unpaid request. The resource server returns payment requirements, including scheme, network, asset and amount. That response is the moment to compare the charge against policy. Directory data helps choose candidates; the live requirement decides whether the agent should proceed.
| Signal | Use | Limitation |
|---|---|---|
| Directory price | Shortlist and compare | May be older than the next quote |
| 402 quote | Authorize one request | Does not prove useful output |
| Paid-call verification | Trust evidence | One successful call is not an uptime guarantee |
A safer pricing policy
A buyer should combine a maximum amount per request, a maximum workflow budget, an allowed network and an allowlist of endpoints. The policy should stop rather than silently overpay when a price changes. TOLL·402 exposes price and network evidence so those controls can be configured before a wallet is connected.
Related directory entries
Sources and methodology
TOLL·402 distinguishes public claims, registry discovery, unpaid quote checks and settled paid-call verification. Sources below support the visible claims; presence in a registry is not treated as verification.
- TOLL·402 directory data — Curated listing and price fields used for the site.
- x402 buyer quickstart — Authoritative current buyer flow and client packages.
- x402 client/server concepts — Defines the live 402 requirements and retry flow.