Leaderboard / btcnode.uk / endpoint
GET https://btcnode.uk/api/network/connections
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Chain read by llm, confidence 60%
- Latest quote
- $0.001 on Base to 0x6a66…43fc
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 4h ago
- Next probe
- 2026-11-17 23:49 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0x6a66…43fc | default | yes | 3h 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 |
|---|---|---|---|---|---|
| 8h ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint is a Bitcoin node's peer connection count, which is node/chain network state returned to the caller. It fits chain_read best, though the description is brief and 'network connections' could arguably be read as infrastructure telemetry. |
| 24h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 131 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 11h ago | free | 402 | 306 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 17h ago | free | 402 | 164 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 23h ago | free | 402 | 118 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 29h ago | free | 402 | 248 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 35h ago | free | 402 | 110 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |
| 42h ago | free | 402 | 126 ms | v2 | yes | $0.001 | 0x6a66…43fc | — |