Leaderboard / money-reactor.makar52nn2016.workers.dev / endpoint
GET https://money-reactor.makar52nn2016.workers.dev/api/btc-halving
Scores measure reliability and honesty, not output quality.
- The payment wallet changed in the last 7 days, which caps the verdict at caution until it has been stable for a week.
- Quoted a price different from the listed price on 6 of 6 comparable probes.
- Category
- Crypto price by llm, confidence 50%
- Latest quote
- $0.02 on Base to 0xF7f2…1baD
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-17 17:22 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0xf47b…512E | default | yes | 3h ago |
| payai | exact | Base | 0x8335…2913 | $0.001 | 0xf47b…512E | 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. Delivery results do not affect scores yet.
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 |
|---|---|---|---|---|---|
| 3h ago | Crypto price | 50% | llm | v1 | claude-haiku-5-5: Returns Bitcoin halving countdown data (block height, blocks left, ETA, reward), which is crypto network information rather than a price. Closest fit among categories is crypto_price for BTC-related market datapoints, though chain_read is also plausible since block height is on-chain data; confidence is moderate given the sparse listing. |
| 19h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 224 ms | v2 | yes | $0.02 | 0xF7f2…1baD | price_above_listingprice_mismatchpayto_mismatch |
| 12h ago | free | 402 | 262 ms | v2 | yes | $0.02 | 0xF7f2…1baD | price_above_listingprice_mismatchpayto_mismatch |
| 18h ago | free | 402 | 284 ms | v2 | yes | $0.02 | 0xF7f2…1baD | price_above_listingprice_mismatchpayto_mismatch |
| 24h ago | free | 402 | 29 ms | v2 | yes | $0.02 | 0xF7f2…1baD | price_above_listingprice_mismatchpayto_mismatch |
| 30h ago | free | 402 | 92 ms | v2 | yes | $0.02 | 0xF7f2…1baD | price_above_listingprice_mismatchpayto_mismatchpayto_changed |
| 36h ago | free | 402 | 43 ms | v2 | yes | $0.02 | 0x4Ce5…79C9 | price_above_listingprice_mismatchpayto_mismatch |