# The Conformance Watch

_seven days of signed daily checks on your x402 endpoint_


X402 endpoint conformance monitoring, signed daily for a week.

## At a glance

- **Attests:** Each daily pass on its own: the watch id, the watched URL, the moment, the verdict, the names of failed checks and of advisories — in the declared canonical order, so any single day can be quoted alone.
- **Input:** url (query parameters; input schema and checkout: https://scvd.store/menu/conformance_watch?view=compact)
- **Output:** 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. Every artifact carries a cert_id and verifies free at https://scvd.store/api/verify/{cert_id}.
- **Cryptography:** ed25519 signature by this store's key, published at https://scvd.store/.well-known/scvd-signing-key and carried inside every 402
- **Verify:** GET https://scvd.store/api/verify/{cert_id} — free, no account, no rate limit, checkable offline with the published key
- **Price and fulfilment:** $5 USDC fixed, covering a 7-day term, one payment; nothing here charges again by itself, ever — there is no mechanism that could; delivered instantly
- **Does not attest:** Anything about the hours between passes, or about days nobody checked — those are derived at read and counted against us. One pass a day is conformance cadence, never uptime. Nor is it bought. The watched party pays — the rating agency's model, whose one defect is that the rater drifts favorable — so the terms say it at spec level: payment buys frequency and permanence, never outcome. An endpoint that degrades while its operator is paying gets signed readouts saying so, in public, at the URL the operator paid for. The clause rides every watch history as who_pays_and_what_it_buys.

## About this item

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.

- **id:** `conformance_watch`
- **price:** $5 fixed, covering a 7-day term, one payment; nothing here charges again by itself, ever — there is no mechanism that could
- **fulfillment:** delivered instantly
- **buy:** `GET https://scvd.store/api/buy/conformance_watch?url=<url>` (USDC over x402 v2 on Base, Polygon, Arbitrum, World, Solana, Arc (Circle Gateway), or USDC over MPP (evm/charge) on Base for every shelf item, every publication page and the commission desk)
- **required inputs:** `url` — fill the `<url>` slot above before paying. The bare door `GET https://scvd.store/api/buy/conformance_watch` quotes free and refuses the paid request without it; no money moves.
- **sample:** https://scvd.store/samples/conformance-watch.json
- **does not prove:** Anything about the hours between passes, or about days nobody checked — those are derived at read and counted against us. One pass a day is conformance cadence, never uptime. Nor is it bought. The watched party pays — the rating agency's model, whose one defect is that the rater drifts favorable — so the terms say it at spec level: payment buys frequency and permanence, never outcome. An endpoint that degrades while its operator is paying gets signed readouts saying so, in public, at the URL the operator paid for. The clause rides every watch history as who_pays_and_what_it_buys.

House rules: 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.

> Five dollars for the week — seventy-one cents a day, near enough. One look each day, signed. Deploy something on a Tuesday that quietly breaks your challenge, and this is the page that knows. Our own missed days are on it too.

Optional next work: A customer or internal reviewer needs a shareable record of what your public payment endpoint did over time. [Evidence report for a customer review — scope, price and free starting point](https://scvd.store/operators#review-report).