Leaderboard / api.blockchain.info / endpoint
POST https://api.blockchain.info/explorer-gateway-kt/x402/charts/mempool-size
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 days.
- Category
- Chain read by llm, confidence 72%
- Latest quote
- $0.005 on Base to 0x995f…d8e0
- 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
- 3h ago
- Next probe
- 2026-11-18 11:53 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0x995f…d8e0 | default | yes | 5h 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 |
|---|---|---|---|---|---|
| 32h ago | Chain read | 72% | llm | v1 | claude-haiku-5-5: The endpoint serves Bitcoin mempool-size chart data from Blockchain.com's explorer, which is public on-chain network data. The description is generic, so confidence is moderate. chain_read is the closest fit, though crypto_price is less likely since this is network metrics rather than prices. |
| 36h ago | Chain read | 60% | rules | v1 | rule chain_read matched "mempool" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 174 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 10h ago | free | 402 | 186 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 16h ago | free | 402 | 186 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 23h ago | free | 402 | 668 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 29h ago | free | 402 | 223 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 35h ago | free | 402 | 177 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 41h ago | free | 402 | 168 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 2d ago | free | 402 | 169 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |
| 2d ago | free | 402 | 180 ms | v2 | yes | $0.005 | 0x995f…d8e0 | — |