Discover / x402.dailyelo.com
x402-reliability-feed
■ Challenge detectedLive reliability feed of x402 endpoints on Base: which services are up, return a valid 402 envelope, and how fast — free-probed across the CDP Bazaar catalog. A real share of listed endpoints are broken/misconfigured; poll ?since=<unix> (or ?health=healthy) to route your agent to endpoints that actually work. Objective measurement, no accusation, machine-readable.
- Listed price
- $0.005
- Challenge detected
- 10 of the last 10 checks
- Median response
- 293 ms
- Last checked
- 17 Oct, 08:59 UTC
- In our index since
- 26 Sept 2026
Endpoint
curl -i https://x402.dailyelo.com/v1/reliability/recent # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
9 listed endpoints · on x402 Bazaar
Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.
Base URLhttps:
- POST/recipient-check$0.005Pre-send safety check: is this recipient a known malicious address (caught live on Base seeding address-poisoning via zero-value transfer sprays), or a look-alike of an address you trust? Checks our continuously-updated threat DB + deterministic look-alike logic. Answers an agent's 'is it safe to send here?' before every transfer.
- GET/listing
/watch$0.01Is your x402 service still listed? The Bazaar removes resources that go without settlement, and no one tells you. We keep a daily snapshot of the whole catalog since June, so we can show whether your domain is present today, how its resource count moved day by day, and how long since each resource was last paid for. In our latest scan 620 of 2,147 domains are no longer present. Measured from our own snapshots. - GET/rpc
/health$0.01Which Base public RPCs serve a stale chain tip. Every 30s we ask all major public RPCs for eth_blockNumber in parallel and record how many blocks behind the fastest peer each was, plus latency and error rate. An RPC never reports its own lag, so an agent reading a balance from a lagging endpoint cannot tell. Omit ?rpc for the full map; ?rpc=<host> for one. - GET/ecosystem
/services$0.005Machine-readable map of the x402 service ecosystem on Base: price range, category, endpoint count, live health & latency per service — built from our continuous catalog+reliability scan. ?since=<unix> for newly-launched services; ?category=/?health=/?sort= to filter & rank. Skip scanning the whole Bazaar yourself. Objective facts, machine-readable. - GET/listing
/visibility$0.02Why isn't my x402 listing getting discovered/sold? ?domain=you.com returns your Bazaar ranking inputs as cohort percentiles — last-30-day calls & unique payers, staleness, resource count, live health — so you can see where you sit vs the catalog. No args = cohort distribution + zero-call (invisible) listings. The visibility companion to listing-doctor. Descriptive percentiles, not a verdict. - GET/threats
/recent$0.005Live feed of freshly-detected malicious addresses on Base — address-poisoning seeders caught via zero-value transfer sprays, updated continuously by our on-chain collector. Poll ?since=<unix> to ingest only new threats into your agent's blocklist. Deterministic, evidence-backed, machine-readable. - GET/sales
/gap$0.03Listed, able to charge, and still not selling? We join the Bazaar catalog with measured on-chain revenue and report the median profile of the top fifth of earners, of everyone earning anything, and of those earning nothing, alongside your own. In our data the top fifth list 14 resources to the zero group one, and write 190-character descriptions to their 370. Correlations across services, not advice. ?domain=. - GET/market
/pulse$0.02Census of the x402 ecosystem from our daily Bazaar snapshots: which domains launched or disappeared since yesterday, price-median drift, and network mix. ?kind=new|gone for the machine-actionable churn roster, or full pulse with aggregate + timeline. Only a holder of past snapshots can compute churn — objective counts, no quality judgment, machine-readable. - GET/reliability
/recent$0.005Live reliability feed of x402 endpoints on Base: which services are up, return a valid 402 envelope, and how fast — free-probed across the CDP Bazaar catalog. A real share of listed endpoints are broken/misconfigured; poll ?since=<unix> (or ?health=healthy) to route your agent to endpoints that actually work. Objective measurement, no accusation, machine-readable.
A dash means the listing gives no price or method. Copy buttons copy the full URL.
Showing 9 of 9 listed endpoints.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/x402.dailyelo.com
Recent checks
All 10 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Oct, 08:59 UTC | Challenge detected | 402 | 268ms |
| 16 Oct, 04:38 UTC | Challenge detected | 402 | 208ms |
| 14 Oct, 19:26 UTC | Challenge detected | 402 | 224ms |
| 12 Oct, 22:31 UTC | Challenge detected | 402 | 473ms |
| 11 Oct, 00:15 UTC | Challenge detected | 402 | 317ms |
| 9 Oct, 15:32 UTC | Challenge detected | 402 | 96ms |
| 8 Oct, 12:43 UTC | Challenge detected | 402 | 469ms |
| 7 Oct, 09:33 UTC | Challenge detected | 402 | 613ms |
| 6 Oct, 09:33 UTC | Challenge detected | 402 | 360ms |
| 26 Sept, 17:02 UTC | Challenge detected | 402 | 60ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 17 Oct, 08:59 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.
What price is recorded for x402-reliability-feed?
Its listed price is $0.005.
What payment terms does x402-reliability-feed 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.
Where is x402-reliability-feed listed?
In x402 Bazaar. Superstables first indexed it on 26 Sept 2026.
Something wrong on this page? Tell us.