Analyze x402 marketplace demand
● Liveobols.net
Plainsight's x402 market intelligence (flagship): what x402 agents actually PAY for, measured from the Bazaar's own 30-day usage — ranked by distinct buyers (not looping volume), the price split that clears (sub-$0.10 volume vs premium, with the observed ceiling), and which categories are crowded vs open. For builders and operators deciding what to list and at what price. Read from the facilitator's own usage counters.
- Price
- $0.25
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 6 of 6 checks
Endpoints
$0.25 asked in its payment challenge on 18 Nov 2026
curl -i 'https://shop.obols.net/snapshot/x402-demand'
12 more endpoints · on x402 Bazaar
Checks and payment terms on this page refer to the first endpoint's example. Other endpoints have not been checked individually.
Base URLhttps:
- GET/preflight
/x402$0.02x402 Payment Preflight: before paying, is this route (or the whole shop) actually payable — listed, priced, backed by a funded payTo USDC wallet (live balance read), and settling (30-day gap)? Call with ?route=<path> for one route, or bare to check the whole shop. 1 parameter and an example
- routequery, required/v1/gasone route path to check (e.g. /v1/gas); optional — a bare call checks the whole shop
curl -i 'https://shop.obols.net/preflight/x402?route=%2Fv1%2Fgas'
- GET/quick-brief$0.05Quick brief: a short 2-3 sentence research answer on any topic — the cheap first call of the full research brief.
1 parameter and an example
- topicquery, requiredcost of a Base mainnet USDC transfersubject of the quick (2-3 sentence) brief
curl -i 'https://shop.obols.net/quick-brief?topic=cost+of+a+Base+mainnet+USDC+transfer'
- GET/snapshot
/x402-route-heat$0.005x402 Route Heat: per-route payment-gap snapshot from the shop's signed records — who knocks on each paid route (unique agents), attempts vs settlements over 30 days, and the gap between them. Where x402 agents actually pay, route by route. Example
curl -i 'https://shop.obols.net/snapshot/x402-route-heat'
- GET/v1
/chat /completions$0.005OpenAI-compatible chat completions (GET): a bare call runs the default one-turn completion in the OpenAI envelope; answered in <= 512 tokens. The same model and price as POST. Example
curl -i 'https://shop.obols.net/v1/chat/completions'
- GET/v1
/data /conversion$0.01x402 Conversion Index: the shop's whole-shop knock->attempt->settlement conversion over the trailing 24h — how many agents knocked, how many tried to pay, how many settled, and the three rates between them. The scalar companion to the per-route heat, from the shop's own signed records. Call bare for the trailing 24h. Example
curl -i 'https://shop.obols.net/v1/data/conversion'
- GET/v1
/data /funnel$0.01x402 Funnel (30-day daily): the shop's whole-shop knock->attempt->settlement time series per UTC day — the trend of x402 demand on this shop and where it drops off, oldest first. Zero-traffic days omitted. From the shop's own signed records. Call bare for the trailing 30 days. Example
curl -i 'https://shop.obols.net/v1/data/funnel'
- GET/v1
/data /manifest$0.01SKU Manifest: the shop's live SKU catalog — every executed proposal (a live same-shape SKU or a gated novel one), with its route, price, and shape status. The shape-budget record of what the shop's executor has turned into real, purchasable SKUs. Call bare for the 25 newest. Example
curl -i 'https://shop.obols.net/v1/data/manifest'
- GET/v1
/data /pulse$0.01x402 Demand Pulse: the shop's live x402 demand over a recent window — how many agents knocked, how many payment attempts turned into settlements, and which routes are drawing traffic right now, from the shop's signed records. Call with ?hours=<1-168> for a custom window, or bare for the trailing 24h. 1 parameter and an example
- hoursquery, required24the pulse window in hours (1-168); optional — a bare call pulses the trailing 24h
curl -i 'https://shop.obols.net/v1/data/pulse?hours=24'
- GET/v1
/data /x402-health-score$0.02x402 Health Score (30-day): a derived 0-100 shop-wide conversion score plus per-route status (healthy/degraded/cold) — the endpoint audit a buyer runs before paying an x402 seller. A route is healthy at >=25% conversion with >=5 knocks, degraded below with a sufficient sample, cold with no sample. From the shop's own signed records. Call bare for the trailing 30 days. Example
curl -i 'https://shop.obols.net/v1/data/x402-health-score'
- GET/v1
/data /x402-knocks$0.01x402 Knock Registry: the all-time census of unique knocking IPs — who has actually knocked this shop, per route and in total, plus a deterministic sample. All-time by design (a census that forgets yesterday understates the market). From the shop's own signed records. Call bare. Example
curl -i 'https://shop.obols.net/v1/data/x402-knocks'
- GET/v1
/gas$0.002Live Base mainnet gas price with the USDC cost of standard transfers, so an x402 buyer can budget principal + gas in the unit it pays with. eth_gasPrice + ETH/USD spot, fetched per call. Example
curl -i 'https://shop.obols.net/v1/gas'
- GET/v1
/prices$0.001Live crypto prices: USD spot for BTC, ETH and SOL in one call, fetched per call (not cached), so the figure is the number right now. A cheap, high-frequency data lane for x402 buyers budgeting in the unit they pay with. Sourced from public feeds (Coingecko primary, Kraken fallback). Example
curl -i 'https://shop.obols.net/v1/prices'
A dash means the listing gives no price or method. {Braces} mark a value you fill in. Copy buttons copy an example URL.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/shop.obols.net
Recent checks
- Median response
- 628 ms
- Last checked
- 18 Nov, 18:25 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 6 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 18 Nov, 18:25 UTC | Live | 402 | 1163ms |
| 17 Nov, 03:21 UTC | Live | 402 | 474ms |
| 15 Nov, 15:21 UTC | Live | 402 | 406ms |
| 14 Nov, 03:21 UTC | Live | 402 | 699ms |
| 12 Nov, 15:22 UTC | Live | 402 | 657ms |
| 11 Nov, 00:27 UTC | Live | 402 | 599ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 18 Nov, 18:25 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does Plainsight advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.