Endpoint

B

scvd.store/api/buy/recurring_patronage

· score 77/100 · recomputed 30m ago

Task: Hold a standing pass a third party can check is current. Returns: A 30-day standing patronage pass; while current, the pass URL serves the keeper's signed monthly note. 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: none stated. Recurring Patronage, A 30-day standing patronage pass. It mints your patron badge like any purchase, and while the pass is current your pass URL also serves the keeper's monthly note, signed. Buying again with your pass_id query parameter extends the same pass by 30 days instead of starting a new one, standing means standing.

NEW_UNKNOWN
First seen
5d ago
Probes stored
4

Score

B
77 of 100
recomputed 30m 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
5h ago 402 35 ms exact
eip155:8453
0xDD35…9bd0 3.000000 clean
12h ago 402 49 ms exact
eip155:8453
0xDD35…9bd0 3.000000 clean
4d ago 402 23 ms exact
eip155:8453
0xDD35…9bd0 3.000000 clean
4d ago 402 28 ms exact
eip155:8453
0xDD35…9bd0 3.000000 clean

Reference

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