Numbers · x402
What does an x402 call actually cost?
Sato Hub read no x402 payload naming a readable USDC price on a mainnet network in its latest run, so what a call costs is unknown rather than free, as of 2026-09-14.
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.
No endpoint we read declared a price in USDC on a mainnet network. That is unknown — not free, and not evidence that x402 endpoints do not charge. Declaring x402 is free; answering a payment request is not, and how many answer at all is the gap this index sits behind.
- Coverage
- Not yet measured.
- 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
- Not yet measured.
- Related
- Whether these endpoints answer at all is on x402 endpoints that answer, and the per-endpoint table on x402 verified.
Questions this page answers
- What does an x402 call cost?
- No endpoint we read declared a USDC price on a mainnet network, so the answer is unknown rather than free.
- 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.
Sources — the payment protocol these prices are declared under
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.
Cite this page
Sato Hub. "Declared x402 price per call, by capability." Sato Hub, updated 2026-09-14, accessed 2026-09-14. https://satohub.ai/numbers/x402-price-per-callData last refreshed 2026-09-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.