risk data for machine payments
Endpoint
scvd.store/api/buy/passport_refresh
Task: Turn my endpoint passport fresh again right now — a new census observation of my door, without waiting for Sunday's walk. Returns: One fresh observation of your x402 endpoint by the weekly census's own instrument, right now instead of next Sunday — folded into your endpoint passport wherever it is newest, which moves the passport's freshness state (and the free embeddable chip that decays with it) back to fresh. Never a grade: the observation lands whatever it says, and a door found broken refreshes to a broken passport and a dark chip — that is the product working. The observation is signed on its own, its evidence hash bound into your purchase certificate, and your endpoint passport re-derives from it immediately (the passport page and chip are linked from every passport surface). Price: $1 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give your endpoint in the url query parameter: https, default port, on the public internet. We refuse our own hostname; The probe is the census's: one GET, Web Bot Auth signed, byte-comparable with the weekly rounds; The newest observation wins in BOTH directions — a broken finding turns the chip off; One observation at one moment; the standing version is conformance_watch, a different item; The passport and chip stay free to read forever; this buys only the freshness. The Refresh, One fresh observation of your x402 endpoint by the weekly census's own instrument, right now instead of next Sunday — folded into your endpoint passport wherever it is newest, which moves the passport's freshness state (and the free embeddable chip that decays with it) back to fresh. Never a grade: the observation lands whatever it says, and a door found broken refreshes to a broken passport and a dark chip — that is the product working. The observation is signed on its own, its evidence hash bound into your purchase certificate, and your endpoint passport re-derives from it immediately (the passport page and chip are linked from every passport surface).
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 | 97 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
| 8h ago | 402 | 42 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
| 4d ago | 402 | 43 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
| 4d ago | 402 | 24 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
Reference
| URL | https://scvd.store/api/buy/passport_refresh |
| Sources | well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 1.000000 |
| 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.