risk data for machine payments
Endpoint
scvd.store/api/buy/conformance_watch
Task: Catch a deploy quietly breaking my x402 endpoint's payment challenge during the week. Returns: A watch id and a permanent history URL, readable immediately and filling in daily for seven days: one signed pass per day carrying the verdict, every failed check and advisory by name, plus a summary deriving the days the store missed and whether the readout drifted between passes. Bounded and prepaid; ends after seven days, renews only by repurchase. Price: $5 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: The url query parameter (https, default port, on the public internet, the URL a buyer would GET expecting a 402); One pass per day for seven days, each signed alone; first pass on the store's next hourly rounds; The checks are the free preflight's published battery (GET /api/preflight/v1) — same law, daily; Days the store misses are derived at read time and published against us in the history; We refuse our own hostname; the watch ends after seven days and never renews itself; The history URL is free to read forever. The Conformance Watch, Name your x402 endpoint (the url query parameter) and once a day for seven days the store runs the published preflight battery (v1, the frozen structural series — the battery each signed pass names inside its own bytes) against it — the 402 shape, the header, the accepts fields, the structural check on any signed offers in either placement — and signs that day's readout on its own: verdict, every failed check, every advisory, dated. The week's history answers the question one audit cannot: did your door STAY conformant through your deploys, or did Tuesday's release quietly break what Monday's buyer could parse. Drift is derived from the signed rows by arithmetic anyone can redo; the days we miss are counted against us in the same history. Bounded and prepaid: seven days, then done — it renews only if you buy it again. Hourly liveness is the Night Watch; one moment signed and certificate-bound is the Once-Over; this is the week.
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 |
|---|---|---|---|---|---|---|
| 4h ago | 402 | 44 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
| 4d ago | 402 | 22 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
| 4d ago | 402 | 26 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
Reference
| URL | https://scvd.store/api/buy/conformance_watch |
| Sources | bazaar well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 5.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.