# The Night Watch

_seven days of signed hourly probes on your x402 endpoint_


X402 endpoint uptime monitoring, signed hourly for a week.

## At a glance

- **Attests:** Each hourly row on its own: the watch id, the watched URL, the moment, the verdict, the names of any failed checks, and the status and latency where present — in the declared canonical order, so any single row can be quoted alone.
- **Input:** url (query parameters; input schema and checkout: https://scvd.store/menu/standing_watch?view=compact)
- **Output:** A watch id and a free, permanent history URL that fills with one signed observation per hour for seven days, gaps stated. 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 hours we did not probe. The gaps are derived at read and counted against us in the same history; a row is one look from one vantage, never an uptime figure. 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

Day shift included; we just liked the name. Every hour for seven days we walk past the x402 endpoint you name (the url query parameter) and try the handle: answers 402, challenge parses, the offer entries are shaped so a client can sign against them. Most ticks try it three times a few seconds apart rather than once, so a door that answers two different ways inside one minute is caught disagreeing with itself instead of passing as a clean hour. Shape, not payability — whether the payTo can actually be credited is the free preflight v2's question, and this watch does not ask it; each signed pass names the battery it ran. Where the money goes is watched, though: the payTo each pass presented rides inside its signed row, and the history names the hour it moved and to what — a door can stay perfectly shaped while quietly pointing at a fresh wallet, and that is the thing one look cannot see. Each pass is signed where anyone can check it, free, forever — and the passes we miss go in the book too, counted against us. A watchman who leaves his naps out of the log isn't one. Name your own door; that's a rule of the house, not a check we can run. This is the week-long look, hour by hour, signed.

- **id:** `standing_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/standing_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/standing_watch` quotes free and refuses the paid request without it; no money moves.
- **sample:** https://scvd.store/samples/night-watch.json
- **does not prove:** Anything about hours we did not probe. The gaps are derived at read and counted against us in the same history; a row is one look from one vantage, never an uptime figure. 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.

> That'll be $5, friend. Your door goes on the rounds tonight.

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).