svm402-service
Paid API · svm402.com · found in a public registry · checked since 2026-10-16
Client error (4xx) · latest check
GET https://svm402.com/price/:addressNo per-call price knownThe name is the registry's label, not ours. Not reviewed by a person. See 12 endpoints from svm402.com. The URL contains placeholders (such as :address) that callers fill in.
Our checks
An unpaid request weekly, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
0 passed, 3 failed, 27 not run.
Checked weekly. Weekly: fewer than 5 payers, or no usage figure.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 0 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-18 | 0 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-18 | 0 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing nothing yet: no check of the current method has passed. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- —
- Protocols
- none seen yet
- Networks
- solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Terms changes, 90 days
- no valid payment request yet
Price from the registry's payment terms; protocols and networks as the registry states. Definitions
Reported by the registry
- Payers, 30 days
- 3
- Paid calls, 30 days
- 2610
The registry's own figures, not our measurements.
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Financial and economic data / Market data (primary); Financial and economic data / Crypto and on-chain data. Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/4): ✗ what it does is unclear to our placement; ✗ its latest check did not pass; ✗ fewer than 5 payers in 30 days (registry figure).
Purpose tags: solanapre-tradeliquiditymarket-data
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Client error (4xx) HTTP 410 expected 402 payment challenge |
— | 751 ms |
cloudflare:EWR |
Client error (4xx) HTTP 410 expected 402 payment challenge |
— | 348 ms |
cloudflare:LHR |
Client error (4xx) HTTP 410 expected 402 payment challenge |
— | 277 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 3 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_06a8376427dfbe1a