risk data for machine payments
Endpoint
scvd.store/api/buy/settlement_reconciliation
Task: Observe an agent payment's USDC movement against an attributable fixed value or a declared ceiling, stating when no cap is observable. Returns: A signed JSON observation of one Base transaction reconciling two numbers — the USDC that moved and an attributable fixed authorization value or declared cap — with cap_source and cap_observed naming where the ceiling came from and whether we saw it ourselves. Verdicts: within_cap, over_cap, no_discretion (EIP-3009, where the value was fixed in the payer's signed digest), cap_not_observable, or no_settlement. Certificate binds the evidence hash; free public record URL. Instant. Price: $0.006 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 Base transaction hash (0x + 64 hex) in the tx_hash query parameter. This product reads Base only; checkout networks do not change the subject chain; Optional narrowing: payer, recipient — a receipt can carry several legs and the largest match is what gets reported; Optional declared_cap_usdc: recorded as DECLARED, never as observed, and never allowed to override a ceiling found on the chain; Approval alone is not an observed spending cap; a paired EIP-3009 value is; Observes money only, never delivery; Receipt, chain and head checked before payment. Invalid context: retry the same payment. Settlement Reconciliation, Give a Base transaction hash to receive a signed observation of the USDC movement and any attributable authorization limit. A paired EIP-3009 authorization fixes the selected transfer's value: no discretion. An Approval in the same receipt does not establish which allowance funded that transfer. Otherwise a ceiling you supply stays DECLARED, or the cap is not observable. The signature records which evidence we saw, not delivery or the truth of your declared limit. Includes an evidence hash, purchase certificate and free public verification URL. Older approval-based claims need the correction at /corrections.
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 |
|---|---|---|---|---|---|---|
| 5h ago | 402 | 58 ms | exact eip155:8453 |
0xDD35…9bd0 | 0.006000 | clean |
| 4d ago | 402 | 432 ms | exact eip155:8453 |
0xDD35…9bd0 | 0.006000 | clean |
| 4d ago | 402 | 707 ms | exact eip155:8453 |
0xDD35…9bd0 | 0.006000 | clean |
Reference
| URL | https://scvd.store/api/buy/settlement_reconciliation |
| Sources | bazaar well-known |
| Recipient per catalogue | 0xDD350976B8cfFc65938C0464d39A2C78BE079bd0 |
| Price per catalogue | 0.006000 |
| 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.