risk data for machine payments
Endpoint
scvd.store/api/buy/provenance_check
Task: Learn which doors have advertised a receiving address and when, signed from the public chain, before routing money at it — or about my own address, free, once proved. Returns: A signed JSON record — the subject address verbatim and its v1 digest, never_seen, one entry per signed week the address was advertised (week, sequence, snapshot digest, the doors with verdict and offered terms), dated drift between weeks, the subject's standing note verbatim when one exists, the shared-wallet caveat inline, the honest limits and how to rederive — its evidence hash bound into the purchase certificate's attests field, served to the buyer at a stable record URL. Instant; reads the signed chain only, 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 the receiving address in the address query parameter: an EVM address (0x + 40 hex) or a Solana pubkey (base58); Reads the signed chain and nothing else — no request is made to any door, and nothing private feeds it; Delivered to you and never published; no operator field, no score, no identity assertion — pairings and dates only; The subject's standing note rides the artifact verbatim, beside the observation, never instead of it; An address the chain has never seen returns never_seen, which is the answer you paid for; Your own address: GET /api/provenance/self?address= for the challenge, POST it back signed (EIP-191), and the same answer is free. The Company an Address Keeps, Which doors have advertised this receiving address, and when: the hosts, the signed weeks, each week's verdict, drift in the door's own terms, and the snapshot digest behind every line. Rebuild it from the public chain without our word. No judgment: shared addresses are ordinary, custodians are common, and this store does not grade operators. Your own address is free once you prove it is yours (GET /api/provenance/self for the challenge), and that free reading ends with an offer to publish it, which you may decline.
Score
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
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 3h ago | 402 | 74 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
| 10h ago | 402 | 81 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
| 4d ago | 402 | 32 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
| 4d ago | 402 | 33 ms | exact eip155:8453 |
0xDD35…9bd0 | 5.000000 | clean |
Reference
| URL | https://scvd.store/api/buy/provenance_check |
| Sources | well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 5.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.