Endpoint

B

scvd.store/api/buy/launch_check

· score 77/100 · recomputed 1m ago

Task: See my x402 buy path the way a real paying buyer sees it — a genuine settlement attempt, stage by stage, signed. Returns: A signed JSON walk record — verdict (settled, payment_refused, no_payment_gate, malformed_challenge, unpaid_by_rule or unreachable), every stage with its detail (approach, challenge, terms, screen, payment, settle, delivery), what this store paid and to whom, the settlement transaction where the seller returned one, the paying field wallet, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable check URL serving the record free forever. Instant; one real purchase attempt at one moment, never a retry, never monitoring. Price: $5 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; One real purchase attempt, once, from the declared field wallet (house-ledger.json) — never a retry loop, never a monitor; 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; We refuse our own hostname — a settlement report about our own till, signed by us, would be the instrument vouching for itself; The check URL is free to read forever; the settlement, if one happens, is permanently on chain either way. The Launch Check, Name your x402 endpoint (the url query parameter) and this store walks it the way a paying stranger does: one unpaid GET with our declared field-research User-Agent, your 402 challenge read the way a real buyer reads it, the cheapest Base rail chosen, the payTo screened, a real EIP-3009 authorization signed by our declared field wallet, presented, and whatever happens next written down — settled or refused, receipt returned or absent, goods delivered or an empty 2xx. Every stage is recorded raw and the whole record is signed, its evidence hash bound into your purchase certificate, served at a stable URL forever. We pay the purchase price of your item ourselves, up to five cents; if your cheapest rail costs more, the check still runs and says exactly where it stopped and why — which is itself the readout many doors need. Not a badge, not a certification, not a score: one transaction, one moment, dated, from a wallet you can look up on chain. Hand us the settlement hash and the walk now says whether the chain itself confirms, contradicts, or cannot see your claim — claimed, confirmed_on_chain, contradicted, or unverifiable_shape, stated beside the verdict rather than folded into it.

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
77 of 100
recomputed 1m 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
2h ago 402 31 ms exact
eip155:8453
0xDD35…9bd0 5.000000 clean
9h ago 402 81 ms exact
eip155:8453
0xDD35…9bd0 5.000000 clean
4d ago 402 22 ms exact
eip155:8453
0xDD35…9bd0 5.000000 clean
4d ago 402 22 ms exact
eip155:8453
0xDD35…9bd0 5.000000 clean

Reference

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