Back to directory

x402.dailyelo.com

https://x402.dailyelo.com/
● healthy general

Live 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.

Category
general
Chains
eip155:8453
Price
$0.0050–$0.0200 USDC

Quality grade

How grading works
A 76.0 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 200)
Payability 15.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 18.4 / 35
60 distinct payers, 430 USDC transfers in the last 30 days; the wallet is shared by 2 listings, so each is credited 1/2
Performance 10.0 / 10
Last probe answered in 95 ms (full marks at 200 ms or less)
Readiness 12.6 / 15
Agent readiness 84/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 19 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 76.0/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (95 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 15/15 32/32 probes succeeded over 30 days (100%).
Resource declaration 8/10 20 paid resources; 14 sampled lack a description.
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 5/5 seen in a source within 7 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (95 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, bazaar_feed, catalog_listing. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 67% of peers
This listing 84 · peer median 78
Latency
Faster than 89% of peers
This listing 95 ms · peer median 205 ms

Where it loses the most points, and how to win them back

  • Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (95 ms).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
  • Resource declaration −2 — Declare each paid resource with its input and output schema.
    Now: 20 paid resources; 14 sampled lack a description.

How many agent tools actually work · All statistics

Paid endpoints

20 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

https://x402.dailyelo.com/v1/sign-decode
https://x402.dailyelo.com/v1/listing-doctor
https://x402.dailyelo.com/v1/address-poison-check
https://x402.dailyelo.com/v1/approval-risk
https://x402.dailyelo.com/v1/recipient-check
https://x402.dailyelo.com/v1/threats/recent
https://x402.dailyelo.com/v1/reliability/recent
https://x402.dailyelo.com/v1/ecosystem/services
https://x402.dailyelo.com/v1/preflight
https://x402.dailyelo.com/v1/reliability/broken
https://x402.dailyelo.com/v1/infra/platform-health
https://x402.dailyelo.com/v1/market/pulse
https://x402.dailyelo.com/v1/catalog/changes
https://x402.dailyelo.com/v1/listing/visibility
GET https://x402.dailyelo.com/v1/sales/gap

Listed and able to charge but not selling? Attribute profile of the top fifth of earners vs the zero-revenue group, next to yours. ?domain=you.com.

GET https://x402.dailyelo.com/v1/payment/debug

Would a real payment to you actually be accepted? Live verify against the CDP facilitator (no settlement) with the failure reason verbatim. ?url= or ?domain=.

GET https://x402.dailyelo.com/v1/buyers/profile

Who pays you and what else they buy: distinct payers, repeat rate, and the share of your buyers active on other x402 services. ?domain=you.com.

GET https://x402.dailyelo.com/v1/listing/watch

Is your listing still in the Bazaar? Daily catalog snapshots since June: presence, resource count over time, days since last payment. ?domain=you.com.

GET https://x402.dailyelo.com/v1/revenue/scope

What your x402 service actually earns and how that ranks among peers: real USDC inflows measured across the whole catalog. ?domain=you.com.

GET https://x402.dailyelo.com/v1/rpc/health

Which Base public RPCs serve a stale chain tip: blocks-behind-fastest-peer, latency, error rate, probed in parallel every 30s. ?rpc=<url> to look up one.

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://x402.dailyelo.com/  # expect HTTP 402 Payment Required (about $0.005/call)
/.well-known/x402.json
https://x402.dailyelo.com/.well-known/x402

Listed in

Directories this entry was found in.

cdp-bazaar since 2026-06-13 awesome-x402 since 2026-07-26 x402scan since 2026-09-13 x402 since 2026-10-10