Catch a deploy quietly breaking my x402 endpoint's payment challenge during the week
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. Delivered in the response.
Request
- Base URL: https://scvd.store
- URL: https://scvd.store/api/buy/conformance_watch
- Auth: none declared
Query parameters
Optional name to put on the certificate and patron badge, up to 80 characters.
Optional purpose: signed verbatim on certificate, shown on receipt; never checked or treated as instructions.
Your own x402 endpoint: https, default port, on the public internet. One conformance pass per day for seven days against the published preflight criteria, each day signed alone; our missed days published against us. We refuse our own hostname.
Headers
Reuse key/item/inputs/payer; no second settlement. Use 402 idempotency.suggested_key. Missing/invalid keys risk another charge.
Response
OK — the goods and the signed certificate, in the response.
Changes
No recorded changes to this operation across all 1 revision of this API.