Endpoint

B

scvd.store/api/buy/operator_statement

· score 77/100 · recomputed 34m ago

Task: Have my receiving address read off the chain four times a day for a month by a party that is not me — who paid, how many, how much — signed pass by pass. Returns: A statement id and a permanent history URL, readable immediately and filling in four times a day for 30 days: one signed pass per read carrying its exact block range, chain head, inflows and outflows with counts and totals, and a per-pass tally of who paid (capped and saying so); a summary derived at read with distinct payers, the largest payer's transfers and USDC beside the totals, blocks covered against blocks since the term opened, and the passes we missed counted against us. Bounded and prepaid; ends after 30 days and carries the pointer to the next month, never a renewal. Price: $21 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 address in the wallet query parameter: a 0x EVM address on a supported EVM chain, a base58 pubkey on Solana. USDC on Base by default, Polygon with network=eip155:137, other supported EVM chains with network=<a name or CAIP-2 from the input contract>, Solana with network=solana — one chain per statement, named on every pass with the unit its range counts in (blocks, or slots on Solana); Four reads a day for 30 days, each from the block after the last pass to the chain head, never more than the engine's eleven-hour ceiling in one read; a missed pass is closed by the next one where it can be and counted against us where it cannot; Counts and totals cover every block read; per-pass payer tallies are capped at a named number of distinct addresses and say when they stopped naming; Public chain state only: nothing of yours is fetched, and the address is the whole input; The history URL is free to read forever and ends on its own date; nothing here renews itself. The Operator's Statement, Name your receiving address (the wallet query parameter; Base by default, Polygon with network=eip155:137, other supported EVM chains with network=<a name or CAIP-2 from the input contract>, Solana with network=solana) and for 30 days the store's rounds read every USDC transfer in and out of it, straight off the chain, four times a day: each pass picks up at the block after the last one and is signed alone, so the month stitches into one continuous block range and any single pass can be quoted without the rest. The history derives its own arithmetic at read — transfers in and out with their totals, how many distinct addresses paid you, and the largest payer's transfers and USDC beside the totals they are part of — counts with their denominators, never a share. A pass the rounds miss is a gap counted against us on the same page. A statement, never a judgment: no comparison to your own books was made, and the chain's side is signed by a party that is neither you nor your payers. Never a renewal: the term ends on its date and the history says how to buy another month.

NEW_UNKNOWN
First seen
5d ago
Probes stored
3

Score

B
77 of 100
recomputed 34m 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
4h ago 402 85 ms exact
eip155:8453
0xDD35…9bd0 21.000000 clean
4d ago 402 23 ms exact
eip155:8453
0xDD35…9bd0 21.000000 clean
4d ago 402 24 ms exact
eip155:8453
0xDD35…9bd0 21.000000 clean

Reference

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

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.