Endpoint

B

scvd.store/api/buy/the_case_file

· score 77/100 · recomputed 53m ago

Task: Hand the person deciding what went wrong with one agent purchase everything a neutral party observed about it, in one signed file, with what it did not observe stated. Returns: A signed JSON case file — settlement, reconciliation (EVM), mandate with declared cap beside settled amount, the door over the seven days around the transaction with the passport tier at the time, delivery where observed, your declared claim verbatim, and every absent section with its reason — dated, its evidence hash bound into the purchase certificate's attests field, plus a stable /case/{id} URL serving the record free forever. Instant; the chain is read once for the settlement and the reconciliation, the rest from this store's own records. Never a verdict. Price: $0.25 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 the transaction hash in the tx_hash query parameter: 0x + 64 hex for Base or Polygon, a base58 signature for Solana — the shape picks the chain; Optional: mandate_id, url (the endpoint paid), payer, recipient, expected_amount_usdc, launch_check_id; Optional claim: your own account, up to 1000 characters, stored verbatim and marked declared — never checked, never allowed to change an observed field; Identical transaction and declared inputs inside 24 hours reuse the same case file; changed claims or evidence inputs require a new assembly; Reconciliation is EVM only; a Solana purchase gets that section as absent, with the reason; No verdict, ever: the file never says who was wronged, at fault, or liable. The Case File, Give a transaction hash and this assembles, at one moment and under one signature, everything this store already observed about that purchase: a fresh settlement attestation; the reconciliation of movement against an observed fixed value or declared cap (Base); the mandate you cite, its declared cap printed beside the settled amount and never enforced; the door over the seven days around the transaction — corpus rounds, any watch rows, the passport tier at the time — or not_observed, which is an answer about our books; and delivery, if you hold a launch check or this store itself was the seller, otherwise 'delivery not observed by this store' in full weight, because that is the section a dispute usually turns on and we usually do not have it. Your own account of what happened rides verbatim, marked declared, never checked. Every absent section is listed with its reason and counted against us. It says what was observed and what was not; it never says who was wronged. If this store is a party to the purchase, the file says so on its face and still assembles.

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
77 of 100
recomputed 53m 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
1h ago 402 52 ms exact
eip155:8453
0xDD35…9bd0 0.250000 clean
8h ago 402 81 ms exact
eip155:8453
0xDD35…9bd0 0.250000 clean
4d ago 402 23 ms exact
eip155:8453
0xDD35…9bd0 0.250000 clean
4d ago 402 28 ms exact
eip155:8453
0xDD35…9bd0 0.250000 clean

Reference

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