Agent Tools
List
Back to directory

svm402-service — Payment Lab

https://svm402.com/v1/echo
● healthy utility

The svm402-service Payment Lab (issues #247-#251): paid micro-payment lab routes settled with x402 v2 exact-scheme USDC (integer base-unit strings), 17 deterministic failure scenarios on the real verify/settle machinery, on-chain settlement receipts, a free 0-RPC status snapshot and a free signed-payment grader. Paid routes answer 402 + PAYMENT-REQUIRED first; paid amounts appear in x-x402-pric...

Category
utility
Chains
solana, solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp
Price
$0.0020 USDC / call

Quality grade

How grading works
B+ 69.1 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 402)
Payability 15.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 13.0 / 35
7 distinct payers, 373 USDC transfers in the last 30 days; discounted because most transfers come from few payers
Performance 8.1 / 10
Last probe answered in 539 ms (full marks at 200 ms or less)
Readiness 13.0 / 15
Agent readiness 86/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 18 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 69.1/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 25/25 Paid endpoint answers with an HTTP 402 challenge (539 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 9.84/15 21/32 probes succeeded over 30 days (66%).
Resource declaration 10/10 Declares 8 paid resource(s).
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 5/5 seen in a source within 7 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (539 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, catalog_listing. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 74% of peers
This listing 86 · peer median 78
Latency
Faster than 16% of peers
This listing 539 ms · peer median 205 ms

Where it loses the most points, and how to win them back

  • Uptime (30 days) −5.2 — Stay reachable in our daily probes.
    Now: 21/32 probes succeeded over 30 days (66%).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.

How many agent tools actually work · All statistics

Paid endpoints

8 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

GET https://svm402.com/v1/ping

The smallest paid lab call — one request proves the WHOLE x402 v2 round trip: the 402 challenge, your signed exact-scheme USDC transfer, the facilitator verify + settle, and a 200 whose payment block carries the payer, the settled amount (integer USDC base units), the transaction hash, the explorer

POST https://svm402.com/v1/echo

Paid mirror for client debugging: after your payment settles the response echoes exactly what the gateway received — HTTP method, path, the RAW query string, the parsed JSON body (≤ 16 KB; a bigger body 413s BEFORE any settle), sha256 over the raw bytes and an allowlisted headers_seen where the paym

GET https://svm402.com/v1/scenarios

The free scenario engine manifest (#248): each walk's name, method, per-network price (integer USDC base units), whether it settles, its mainnet policy (yes / opt-in / devnet-only), its params, the expected status sequence and the live lab store metrics (issued / redeemed / expired / charged_unserve

GET https://svm402.com/v1/scenario/{name}

One #248 fault walk (17 deterministic machines: ok — a clean serve; slow — a slowed serve (the sleep is real, the decision is clock-free); verify_reject — a verify-time rejection (a fresh challenge, nothing settled); retryable_503_before_settle — a retryable 503 after verify, BEFORE settle; price_ch

GET https://svm402.com/v1/scenario/redeem

The free recovery lane (#248): ?client_id= (or X-Lab-Client-Id) serves a previously settled but unserved scenario charge ONCE — binding-first (exact path + body fingerprint + payer), single-use, outcome-closed; an unknown/expired/consumed credential answers 404 with the manifest pointer, never an er

GET https://svm402.com/v1/receipt/{signature}

The paid #250 receipt: ONE getTransaction through the shared lab RPC token bucket, cached by chain finality (finalized/failed forever, not_found/confirmed/processed 10 s). The body reports the chain status, slot, block time, fee lamports, fee payer (labeled — 'own' is the facilitator fee payer THIS

GET https://svm402.com/v1/status

The free #250 status: every facilitator's probe health (last_probe_at, probe_ms_p50, the 3-failure breaker), the lab's 24 h settles / charged-unserved / open credentials (timestamped SQL), the OWN fee-payer balance (a background refresher — the route never calls RPC) and the 24 h ping p95. #299: the

POST https://svm402.com/v1/diagnose

The free #249 grader: 43 offline checks (envelope ↔ challenge ↔ wire — accepted-copy mismatches including the stale fee payer, the client's ed25519 signature over the exact message bytes, transferChecked semantics, compute-budget discipline, the optional memo tail, and since #294 the challenge's res

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X POST https://svm402.com/v1/echo  # expect HTTP 402 Payment Required (about $0.002/call)
/.well-known/x402.json
https://svm402.com/.well-known/x402

Listed in

Directories this entry was found in.

x402scan since 2026-05-22