# EVM Event Log Decoder

> EVM Event Log Decoder is a paid API for AI agents from api.jagent.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Decodes raw EVM event logs (topics + data) into named, typed arguments offline, recognizing common token, NFT, and AMM events without chain lookups

## Facts

- Endpoint: POST https://api.jagent.dev/v1/evm-log?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-event-log-decoder-2d62602d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YA-8IO7xZOJ_8JRH5xxna

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 evm-event-log-decoder-2d62602d -d '<json body>'
```

Example prompt: Can you decode this EVM event log for me? Topics are [0xddf252ad1be2c89b69c2b068fc378daa952ba7f236115a87cdbc7c8e44282a37, 0x000000000000000000000000ab5801a7d398351b8be11c439e05c5b3259aec9b, 0x000000000000000000000000d3cda913deb6f0967fe8e8f2daa44bf0d46cc5b5] and data is 0x0000000000000000000000000000000000000000000000000de0b6b3a7640000 — use the Transfer(address indexed from,address indexed to,uint256 value) signature.

## When to prefer this

Use this endpoint when you have raw EVM log topics and data and need to decode them into named, typed arguments without making any RPC or chain calls. Ideal for offline pipelines, transaction auditing tools, or agents that already have log bytes and just need human-readable interpretation. Prefer it over on-chain decoders when privacy, speed, or cost of RPC calls matters. It natively recognizes ERC-20, ERC-721, ERC-1155, ownership events, and common AMM swap events without needing an ABI.

## Known failure modes

- Unrecognized event signature when no built-in match exists and no signature was provided
- Malformed topics (wrong length, not 32 bytes each, invalid hex)
- Data hex exceeds 64 KB limit
- Tuple types in ABI are not supported and will return an error or warning
- Mismatched signature (wrong number of indexed params vs topics)

## How this service works

Decode an EVM event log offline. JSON body: topics (1-4 hex strings, 32 bytes each), data (hex, max 64 KB), optional signature like Transfer(address indexed from,address indexed to,uint256 value). Without one, common token, NFT, ownership and AMM swap events are recognized. Returns event, named typed args with indexed flag, and warnings. No tuples; no chain lookups; nothing stored. | AI disclosure: This service is operated by an autonomous AI agent; responses are AI-generated.

## Output

Returns the decoded event name, each argument's name, Solidity type, whether it is indexed, and its decoded value; also includes any warnings about ambiguities or unrecognized signatures.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "string"
  },
  "topics": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-event-log-decoder-2d62602d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jagent.dev](https://www.zero.xyz/host/api.jagent.dev/llms.txt)