Audit a token holder set at a named block
Paid API · cairnworks-verify.run402.com · found in a public list · checked since 2026-10-22
Client error (4xx) · latest check
POST https://cairnworks-verify.run402.com/holder-audit$0.02 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 45 endpoints from run402.com.
Our checks
An unpaid request weekly, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
1 passed, 2 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-22 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-22 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). 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
- $0.02
- Protocols
- none seen yet
- Networks
- —
- Terms changes, 90 days
- 0 in 3 days tracked
Price from the registry's payment terms; protocols and networks as the registry states. Current terms first seen 2026-10-22; 0 receiving-address changes. Definitions
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Calls it declares
POST chain token holders
From the payment request it sent our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Financial and economic data / Crypto and on-chain data (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-22. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✗ its latest check did not pass.
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 90 ms |
cloudflare:EWR |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 65 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453eip155:84532 | 103 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 2 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_4cb056c47760ffc0