Open my x402 endpoint properly — one real purchase attempt, a week of signed daily checks, and my passport page, under one certificate at one URL
Name your x402 endpoint (the url query parameter) and three things happen under one certificate. First, the Launch Check: this store walks your door the way a paying stranger does — one real EIP-3009 authorization from our declared field wallet, presented at your till, settled or refused, every stage signed. Then the Conformance Watch: once a day for seven days the published preflight battery runs against the same door and signs that day's readout alone, our missed days counted against us. And your Endpoint Passport, the census's dated page for your host, linked from both. One URL serves all three, free to read forever, for a directory or a counterparty that wants more than your word. Bought apart these cost ten dollars and come as a receipt each. Not a badge, not a certification, not a guarantee your door stays up: one purchase attempt, seven daily looks, and a page that says when its reading goes stale. Delivered in the response.
Request
- Base URL: https://scvd.store
- URL: https://scvd.store/api/buy/opening_day
- 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, the URL a buyer would GET expecting a 402. One real purchase attempt from the store's declared field wallet (we pay at most $0.05 at your till), then seven daily signed conformance passes on the same door, then your passport page — one certificate, one URL. 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.