# LogicNodes EVM Log Decode

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

Decodes a raw EVM event log into human-readable fields using a provided ABI and log topics/data

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/evm_log_decode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-evm-log-decode-c7e2bb1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_85jyC-c4k_IE1SHpIY6Vm

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-log-decode-c7e2bb1e -d '<json body>'
```

Example prompt: Decode this raw EVM log for me — here's the ABI with the Transfer event signature, the data field is 0x000...0064, and the topics are [0xddf252..., 0x000...abc, 0x000...def]. What event was emitted and what are the decoded parameter values?

## When to prefer this

Use this endpoint when you have a raw EVM log (topics + data) from a transaction receipt and need to decode it into human-readable fields without running your own Ethereum node or indexer. Ideal for agents processing on-chain events programmatically, auditing smart contract activity, or building DeFi analytics pipelines. Prefer this over general-purpose RPC nodes that don't offer ABI-based decoding, and over block explorers when you need machine-readable decoded output rather than a web UI.

## Known failure modes

- ABI does not match the log topic selector — returns error indicating no matching event
- Malformed hex in topics or data — returns parsing error
- topics array length mismatch for indexed parameters — decoding fails
- ABI array is empty or missing required event definition — validation error
- Payment not provided or insufficient USDC — 402 response before processing

## 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

A JSON object with ok:true and the decoded event name, along with the named parameters and their typed values extracted from the raw log topics and data fields.

## 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"
  },
  "topics": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 4,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-evm-log-decode-c7e2bb1e/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)