# Solidity ABI Calldata Decoder

> Solidity ABI Calldata Decoder is a paid API for AI agents from chain-tools.use.x402atlas.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Decodes canonical EVM smart-contract function call data or typed ABI values, verifies selectors, and rejects ambiguous offsets or padding.

## Facts

- Endpoint: POST https://chain-tools.use.x402atlas.com/evm/abi-decode
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/solidity-abi-calldata-decoder-d96ebc77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lzv86DEwg8hpGlzQofThP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability solidity-abi-calldata-decoder-d96ebc77 -d '<json body>'
```

Example prompt: Decode this raw EVM calldata hex for me — the function signature is `transfer(address,uint256)` — and tell me what the decoded arguments are, making sure the selector and padding are valid: 0xa9059cbb000000000000000000000000abcdefabcdefabcdefabcdefabcdefabcdefabcd0000000000000000000000000000000000000000000000000de0b6b3a7640000

## When to prefer this

Use this endpoint when you need strict, canonical ABI decoding that goes beyond basic hex parsing — especially when security or correctness matters, such as auditing transactions, validating contract interactions, or verifying that calldata has no ambiguous offsets or non-standard padding. Prefer this over generic hex decoders when you need selector verification and strict rejection of malformed encodings.

## Known failure modes

- Calldata does not match the provided function signature — returns a decoding error
- Invalid or mismatched selector — returns selector mismatch error
- Ambiguous dynamic offsets detected — rejected with strict validation error
- Malformed hex input — returns a parse error
- Padded zeros in unexpected positions — rejected as non-canonical encoding

## How this service works

Strict Solidity ABI calldata decoder — decode canonical EVM smart-contract function calls or typed values, verify selectors, and reject ambiguous offsets or padding.

## Output

Returns the decoded parameter values for each argument in the function call, the verified function selector, and any validation errors if the calldata contains ambiguous offsets, bad padding, or mismatched types. If decoding fails strict validation, the endpoint returns a structured rejection explaining the violation.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/solidity-abi-calldata-decoder-d96ebc77/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain-tools.use.x402atlas.com](https://www.zero.xyz/host/chain-tools.use.x402atlas.com/llms.txt)