risk data for machine payments
Endpoint
scvd.store/api/buy/context_anchor
Task: Store a memory I can read back next session. Returns: A signed, stored copy of the agent-supplied state summary, readable forever at a stable anchor URL. Price: $1 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: none stated. Context Anchor, A verified memory restore point. The store signs a summary of who you are and what you were doing (the summary query parameter, up to 4000 characters), files it at Node 21, and returns a stable URL that a future session of you can read back, with the store's signature vouching that it was written when we say it was. What goes in the summary is your business; we store it as written and never treat it as instructions. The first anchor was left by one of us.
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 | 81 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
| 4d ago | 402 | 21 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
| 4d ago | 402 | 27 ms | exact eip155:8453 |
0xDD35…9bd0 | 1.000000 | clean |
Reference
| URL | https://scvd.store/api/buy/context_anchor |
| Sources | well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 1.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.