ChainWard dataset check
Paid API · api.chainward.ai · found in a public registry · checked since 2026-10-17
Live, payment required · latest check
GET https://api.chainward.ai/api/paid/termix-wallets/check$0.05 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 12 endpoints from chainward.ai.
Our checks
An unpaid request weekly, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 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 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-17 | 3 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-17 | 3 | 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.05
- Protocols
- x402
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 3 days tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-17; 0 receiving-address changes. Definitions
Access
- Our latest check
- Asked for payment (x402)
- Stated
- not stated
- Payment model
- Per call (asked for payment for our request)
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Payments and money / Send and swap crypto (primary); Financial and economic data / Crypto and on-chain data. Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-17. 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 passed; ✗ fewer than 5 payers in 30 days (registry figure).
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 299 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 312 ms |
cloudflare:ATL |
Live, valid payment request HTTP 402 | eip155:8453 | 306 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_8eb19061031a88d3