Endpoint

B

scvd.store/api/buy/opening_day

· score 77/100 · recomputed 14m ago

Task: 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. Returns: The launch check's signed JSON walk record (verdict, every stage, what was paid, the settlement transaction where one came back), its evidence hash bound into the purchase certificate's attests field; a conformance watch opened on the same door for seven days, each daily pass signed alone at a history URL; the host's endpoint passport URL; and one bundle URL (/api/opening-day/{cert_id}) naming all three, free to read forever. Instant to open; the week fills in day by day and never renews itself. Price: $9 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: Give your x402 endpoint in the url query parameter: https, default port, on the public internet; The launch check is one real purchase attempt from the declared field wallet, once — never a retry loop; We pay at most $0.05 at your till; a costlier cheapest rail gets a signed record of exactly where the check stopped instead of a payment; The payTo is sanctions-screened before any payment, and no screen means no payment — the rule fails closed; The watch is one pass a day for seven days, each signed alone; it ends after seven days and never renews itself; We refuse our own hostname — a report about our own till, signed by us, would be the instrument vouching for itself; The bundle URL, the check URL and the watch history are free to read forever. The Opening Day, 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.

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
77 of 100
recomputed 14m ago

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

WhenCodeLatencyScheme and network RecipientPriceFindings
39m ago 402 39 ms exact
eip155:8453
0xDD35…9bd0 9.000000 clean
7h ago 402 79 ms exact
eip155:8453
0xDD35…9bd0 9.000000 clean
4d ago 402 28 ms exact
eip155:8453
0xDD35…9bd0 9.000000 clean
4d ago 402 23 ms exact
eip155:8453
0xDD35…9bd0 9.000000 clean

Reference

URLhttps://scvd.store/api/buy/opening_day
Sourceswell-known
Recipient per catalogue0xDD350976B8cfFc65938C0464d39A2C78BE079bd0
Price per catalogue9.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.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.