EVM & Solana Utility Tools
Paid API · chain-tools.use.x402atlas.com · found in a public registry · checked since 2026-10-16
Client error (4xx) · latest check
POST https://chain-tools.use.x402atlas.com/evm/abi-decode$0.005 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 236 endpoints from x402atlas.com.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
0 passed, 3 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Payment terms
- Price per call
- $0.005
- Protocols
- none seen yet
- Networks
- eip155:8453eip155:137eip155:42161solana: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
- 2
- Paid calls, 30 days
- 3
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 / Crypto and on-chain data (primary). 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/3): ✗ 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: abi-decodesolidity-abievmblockchain-developmentoffline-computation
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 45 ms |
cloudflare:EWR |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 19 ms |
cloudflare:BOM |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 794 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_32c9d75df2806f99