Endpoint
scvd.store/api/buy/onpage_audit
Task: Get a signed readout of what my page actually serves a machine reader — title, metadata, structured data — that I can hand to a third party. Returns: A signed JSON report — verdict (ready, not_ready, unreachable or refused), every check and advisory from the published on-page battery, the blind spots printed on the artifact, dated, its evidence hash bound into the purchase certificate's attests field — plus a stable report URL serving the record free forever. Instant; one GET of the HTML as served, never a render, never monitoring. Price: $3 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 page in the url query parameter: https, default port, on the public internet; One GET at one moment, of the HTML as served; scripts never run, and the report names that blind spot on itself; The criteria are the free desk's published battery (GET /api/onpage/v1); the audit runs those checks and no others; We refuse our own hostname — an audit of ourselves signed by ourselves would be the instrument vouching for itself; The report URL is free to read forever. The Shop Window, Name a public page (the url query parameter) and the store GETs it once, reads the HTML the way a machine passerby does — title, meta description, canonical, robots directives, headings, JSON-LD structured data, link shape — and signs the whole readout: verdict, every check, every advisory, dated. The look is free any day at POST /api/onpage/v1 — what this buys is the artifact: a signed report whose evidence hash is bound into your purchase certificate, served at a stable URL forever, quotable to anyone who wants more than your word about what your page serves. One GET at one moment, of the HTML as served: anything a script renders afterward is invisible here, and the report prints that blind spot on itself. Not an SEO grade, not a ranking claim, not an endorsement.
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 | 42 ms | exact eip155:8453 |
0xDD35…9bd0 | 3.000000 | clean |
| 10h ago | 402 | 25 ms | exact eip155:8453 |
0xDD35…9bd0 | 3.000000 | clean |
| 4d ago | 402 | 26 ms | exact eip155:8453 |
0xDD35…9bd0 | 3.000000 | clean |
| 4d ago | 402 | 33 ms | exact eip155:8453 |
0xDD35…9bd0 | 3.000000 | clean |
Reference
| URL | https://scvd.store/api/buy/onpage_audit |
| Sources | bazaar well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 3.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.