# LogicNodes EVM Calldata Decoder

> LogicNodes EVM Calldata Decoder is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-30).

Decodes raw EVM transaction calldata into human-readable function names and parameter values using a provided ABI or human-readable signatures

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/evm_calldata_decode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-evm-calldata-decoder-8ea442a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ig5mzjWc9d2ku9jMXDu8a

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 logicnodes-evm-calldata-decoder-8ea442a4 -d '<json body>'
```

Example prompt: Can you decode this EVM calldata for me — here's the raw hex: 0xa9059cbb000000000000000000000000abcdef1234...0000000000000000000000000000000000000000000000000de0b6b3a7640000 — and the ABI signature is 'function transfer(address to, uint256 amount)'?

## When to prefer this

Choose this endpoint when you need to reliably decode raw EVM calldata bytes into structured, human-readable function calls and parameters. It is ideal for AI agents that need exact, deterministic decoding without hallucination risk, supports both JSON ABI objects and human-readable signatures, and is priced per-call in USDC via x402 making it suitable for autonomous agent workflows.

## Known failure modes

- Invalid or malformed hex calldata returns a decoding error
- ABI does not match the function selector in the calldata (function not found)
- Empty or missing ABI array causes validation failure
- Calldata too short or truncated leading to incomplete decoding
- Mismatched parameter types between ABI and encoded data

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

Returns a JSON object with ok=true, the tool name, and the fully decoded calldata including the matched function name, input parameter names, types, and their decoded values extracted from the raw hex data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "abi": {
   "type": "array",
   "items": {
    "anyOf": [
     {
      "type": "object",
      "propertyNames": {
       "type": "string"
      },
      "additionalProperties": {}
     },
     {
      "type": "string",
      "maxLength": 1000
     }
    ]
   },
   "maxItems": 500,
   "minItems": 1,
   "description": "JSON ABI objects, or human-readable signatures such as \"function transfer(address to, uint256 amount)\""
  },
  "data": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "evm_calldata_decode"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-evm-calldata-decoder-8ea442a4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from logicnodes.io](https://www.zero.xyz/host/logicnodes.io/llms.txt)