Leaderboard / x402.glassnode.com / endpoint
GET https://x402.glassnode.com/v1/metrics/addresses/active_count
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
- Crypto market data by llm, confidence 60%
- Latest quote
- $0.05 on Base to 0x1f81…39f1
- 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-17 23:41 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.05 | 0x1f81…39f1 | default | yes | 8m 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 | Crypto market data | 60% | llm | v1 | claude-haiku-5-5: Glassnode on-chain metrics for active address counts are crypto analytics rather than raw chain reads or price data; the closest fit among the categories is crypto_market, though chain_read is a plausible alternative since the data derives from on-chain activity. |
| 25h ago | Crypto market data | 60% | rules | v1 | rule crypto_market matched "on-chain analytics" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 503 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 12h ago | free | 402 | 189 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 18h ago | free | 402 | 485 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 24h ago | free | 402 | 526 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 30h ago | free | 402 | 167 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 36h ago | free | 402 | 476 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |
| 42h ago | free | 402 | 520 ms | v2 | yes | $0.05 | 0x1f81…39f1 | — |