Leaderboard / diamond.btc-intel.workers.dev / endpoint
GET https://diamond.btc-intel.workers.dev/api/x402/tx_eta
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 7 probes; it may no longer be an x402 endpoint.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Category
- Chain read by llm, confidence 60%
- Latest quote
- — on — to —
- 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
- 6h ago
- Next probe
- 2026-11-17 23:34 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0x440D…9D7e | default | yes | 1h 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 |
|---|---|---|---|---|---|
| 10h ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint reports mempool and confirmation status for a Bitcoin transaction (fee rate, projected block, confirmations), which is on-chain state read, though it is also a fee-estimation signal. chain_read fits best because it returns facts about a chain transaction's inclusion status. |
| 26h 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 |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 404 | 1098 ms | — | no | — | — | not_foundstatus_not_402 |
| 13h ago | free | 404 | 1307 ms | — | no | — | — | not_foundstatus_not_402 |
| 19h ago | free | 404 | 1075 ms | — | no | — | — | not_foundstatus_not_402 |
| 25h ago | free | 404 | 1429 ms | — | no | — | — | not_foundstatus_not_402 |
| 31h ago | free | 404 | 998 ms | — | no | — | — | not_foundstatus_not_402 |
| 37h ago | free | 404 | 1256 ms | — | no | — | — | not_foundstatus_not_402 |
| 43h ago | free | 404 | 1239 ms | — | no | — | — | not_foundstatus_not_402 |