What does an x402 call actually cost?
What x402 endpoints declare they charge per call, by price.
- As of2026-10-26
Declared, not charged
Every figure below is read out of the HTTP 402 payload the endpoint itself serves — what the seller says the next call will cost. Nobody paid it. The field is maxAmountRequired, a ceiling rather than a price, so the settled amount can be less. None of this is evidence that paying works, that the seller delivers, or that these are prices anyone has been charged.
| Capability | Network | Median / call | Range | Sellers | Quotable? |
|---|---|---|---|---|---|
| price-feed | eip155:8453 | 0.002 USDC | — | 1 | below the floor |
| onchain-data | eip155:8453 | 0.021 USDC | 0.002–0.04 | 2 | below the floor |
| swap-quote | eip155:8453 | 0.0012 USDC | — | 1 | below the floor |
| inference | eip155:8453 | 0.002 USDC | — | 1 | below the floor |
| search | eip155:8453 | 0.04 USDC | — | 1 | below the floor |
| other | eip155:8453 | 0.05 USDC | 0.005–5 | 6 | below the floor |
Every bucket above sits below the 20-seller floor this site publishes a statistic on. The readings are real and are shown with their counts; none of them is presented as what x402 costs, and a handful of sellers is never multiplied into a market.
- Coverage
- 12 of 10 declared endpoints read named a readable USDC price on a mainnet network.
- Excluded
- Nothing on the latest run. A price in an asset we cannot identify as USDC, or declared on a testnet, is left out and counted rather than converted or compared.
- Capability
- A capability is Sato Hub's reading of the listing's own category and tags and of the path the seller published. It describes what is offered, never that it works, is safe, or delivers. No payment was made to find out. An endpoint matching two rules appears under both.
- Method
- The `maxAmountRequired` (or `amount`/`price`) field of the first payment term in the HTTP 402 payload the endpoint itself served, with the `asset` and `network` it declared beside it. Read in the asset's own base units per the x402 spec (a value containing a decimal point is read as whole units instead). No payment was sent, so no price here was ever charged or settled.
- Related
- Whether these endpoints answer at all is on x402 endpoints that answer, and the per-endpoint table on x402 verified.
Data CC-BY-4.0 — attribution: data by satohub.ai. Declared prices only; no payment has been sent, and unknown is a value here rather than a zero.
Reference
QuestionsWhat people ask about this pageShowHide
Questions this page answers
- What does an x402 call cost?
- Median declared price per call (read 2026-10-26): price-feed on eip155:8453: 0.002 USDC across 1 seller; onchain-data on eip155:8453: 0.021 USDC across 2 sellers (0.002–0.04); swap-quote on eip155:8453: 0.0012 USDC across 1 seller; inference on eip155:8453: 0.002 USDC across 1 seller; search on eip155:8453: 0.04 USDC across 1 seller; other on eip155:8453: 0.05 USDC across 6 sellers (0.005–5). Each is the median across the sellers in that bucket on that settlement network — never across networks, and never across assets.
- Has anyone actually paid these prices?
- No, and the page would be dishonest if it implied otherwise. Every figure is read out of the HTTP 402 payload the endpoint itself serves — what the seller says the next call costs. No payment is ever sent, so nothing here shows that paying works, that the seller delivers, or that the price is what anyone is charged.
- Is the declared price the price?
- It is a ceiling. The field is maxAmountRequired: the most the seller will take for that call. The settled amount can be less, and nothing on this page observes a settlement.
- Why are some prices missing from the index?
- Nothing was excluded on the latest run. Where a price is denominated in an asset we cannot identify as USDC, or declared on a testnet, it is left out and counted rather than converted or compared.
- How is a capability decided?
- From the path the seller published and the listing's own category and tags — price-feed, onchain-data, swap-quote, inference, storage, search, identity, or "other" when nothing matched. "Other" is a real answer, not a guess. An endpoint that matches two rules is counted under both, because it sells both.
- Which of these medians can be quoted as a finding?
- None of them yet. Every bucket is below the 20-seller floor this site publishes a statistic on, so the readings are listed with their counts and no median is presented as the price of anything.
SourcesWhere the data comes fromShowHide
Sources — the payment protocol these prices are declared under
Cite this pagePlain text, APA or BibTeXShowHide
Cite this
Sato Hub read x402 prices from 12 endpoints, but too few sellers offer any one service to publish a typical price yet, as of 2026-10-26.
Sato Hub, "What does an x402 call actually cost?", https://satohub.ai/numbers/x402-price-per-call, as of 2026-10-26. Data CC-BY.
How this was measured
- Method
- The median of the price each seller declares (`maxAmountRequired`) in the HTTP 402 payload its own endpoint served, per capability and network, in USDC on mainnets only; no payment is sent, so it is a declared ceiling, not a charge.
- Window
- The latest weekly reading.
- Data date
- MCP call
onchain_agent_get_agent_economy({"venue":"x402"})on https://satohub.ai/api/mcp- URL
- https://satohub.ai/api/export/adoption.json?venue=x402
The medians are the rows whose stage starts with price_median_usdc:, one per capability and network.
Machine source
- JSON export: https://satohub.ai/api/export/adoption.json → rows where venue="x402" and stage starts with "price_median_usdc:"