Leaderboard / check.blockpin.dev / endpoint
GET https://check.blockpin.dev/check
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.01 on Base to 0x8672…db66
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-17 23:20 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | eip155:4663 | 0x5fc5…d168 | 100000 | 0x8672…db66 | default | yes | 2h ago |
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x8672…db66 | default | yes | 2h 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 |
|---|---|---|---|---|---|
| 14h ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint reads onchain contract state and event logs (owner, proxy implementation, admin, pause state, ownership transfer and upgrade events) across public chains, which matches chain_read. It could arguably be a token safety check under crypto_market, but the returned data is primarily raw contract control state and event history from chain reads. |
| 24h ago | Finance data | 60% | rules | v1 | rule finance_data matched "robinhood" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 677 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 11h ago | free | 402 | 237 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 17h ago | free | 402 | 284 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 23h ago | free | 402 | 979 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 30h ago | free | 402 | 196 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 36h ago | free | 402 | 4011 ms | v2 | yes | $0.01 | 0x8672…db66 | — |
| 42h ago | free | 402 | 200 ms | v2 | yes | $0.01 | 0x8672…db66 | — |