risk data for machine payments
Endpoint
x402.chainquery.com/v1/rpc/uptime
chainquery Bitcoin RPC: pay-per-call Bitcoin Core over x402, no API key. Node uptime in seconds from chainquery's independent full node. Bitcoin Core uptime.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 18m ago | 402 | 99 ms | exact eip155:8453 |
0x7Cf4…87ff | 0.005000 | clean |
| 7h ago | 402 | 266 ms | exact eip155:8453 |
0x7Cf4…87ff | 0.005000 | clean |
| 4d ago | 402 | 361 ms | exact eip155:8453 |
0x7Cf4…87ff | 0.005000 | clean |
| 4d ago | 402 | 152 ms | exact eip155:8453 |
0x7Cf4…87ff | 0.005000 | clean |
Reference
| URL | https://x402.chainquery.com/v1/rpc/uptime |
| Sources | bazaar |
| Recipient per catalogue | 0x7Cf45cD775Bdf31a5a96fa0A5805DF0b610D87ff |
| Price per catalogue | 0.005000 |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.