risk data for machine payments
Endpoint
x402.dailyelo.com/v1/rpc/health
Which Base public RPCs serve a stale chain tip. Every 30s we ask all major public RPCs for eth_blockNumber in parallel and record how many blocks behind the fastest peer each was, plus latency and error rate. An RPC never reports its own lag, so an agent reading a balance from a lagging endpoint cannot tell. Omit ?rpc for the full map; ?rpc=<host> for one.
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 |
|---|---|---|---|---|---|---|
| 1h ago | 402 | 32 ms | exact eip155:8453 |
0xD617…41eE | 0.010000 | clean |
| 8h ago | 402 | 17 ms | exact eip155:8453 |
0xD617…41eE | 0.010000 | clean |
| 4d ago | 402 | 16 ms | exact eip155:8453 |
0xD617…41eE | 0.010000 | clean |
| 4d ago | 402 | 11 ms | exact eip155:8453 |
0xD617…41eE | 0.010000 | clean |
Reference
| URL | https://x402.dailyelo.com/v1/rpc/health |
| Sources | bazaar |
| Recipient per catalogue | 0xD617a7145ca56E3ed58d639F9DEC6999B22441eE |
| Price per catalogue | 0.010000 |
| 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.