Leaderboard / api.data4agents.dev / endpoint
GET https://api.data4agents.dev/v1/latency/global
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- Inference by llm, confidence 35%
- Latest quote
- $0.001 on Base to 0xB88b…D0D9
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-18 06:34 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0xB88b…D0D9 | default | yes | 54m ago |
Paid probes
No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.
Delivery checks
Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.
No delivery checks yet. They run inside the weekly paid probe.
Classification history
Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 15h ago | Inference | 35% | llm | v1 | claude-haiku-5-5: The listing says 'LLM Gateway Data' and 'Live Provider Latency', suggesting it reports latency metrics for LLM providers. It is not clearly a model output endpoint, and the category fitting best is uncertain, so confidence is low. The closest fit is inference given the LLM gateway context, but this could also be a monitoring/other data feed. |
| 32h ago | Inference | 60% | rules | v1 | rule inference matched "llm" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 232 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 12h ago | free | 402 | 697 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 18h ago | free | 402 | 672 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 24h ago | free | 402 | 646 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 31h ago | free | 402 | 650 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 37h ago | free | 402 | 615 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 43h ago | free | 402 | 632 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |
| 2d ago | free | 402 | 711 ms | v2 | yes | $0.001 | 0xB88b…D0D9 | — |