# EVM Event Log Decoder

> EVM Event Log Decoder is a paid API for AI agents from defi-shield-hazel.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Decodes raw EVM event log data (topics and data fields) into human-readable event names and typed parameters

## Facts

- Endpoint: POST https://defi-shield-hazel.vercel.app/api/data/event-decode
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-shield-hazel-vercel-app-4105a385
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aFnp3U1unVFEdyK4Gdr-z

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 defi-shield-hazel-vercel-app-4105a385 -d '<json body>'
```

Example prompt: Can you decode this raw EVM event log for me — the log data is 0x0000000000000000000000000000000000000000000000000000000000001000 and the topics are [0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, 0x0000000000000000000000001111111111111111111111111111111111111111, 0x0000000000000000000000002222222222222222222222222222222222222222] — I want to know the event name and the decoded parameter values.

## When to prefer this

Use this endpoint when you have raw EVM transaction receipt log data (hex-encoded data and topics arrays) and need to convert them into human-readable event names and typed parameter values. Ideal for DeFi analytics pipelines, transaction monitoring agents, or any workflow that processes on-chain events from Ethereum, Base, or other EVM-compatible chains and needs structured, interpretable output without running a full node or maintaining a local ABI registry.

## Known failure modes

- Unknown event signature hash — returns no match if the topic0 hash is not in the known events registry
- Malformed hex data — invalid or truncated log_data or log_topics cause parsing errors
- Missing required fields — omitting log_topics or log_data results in a 400-style error
- Ambiguous ABI — logs from unverified contracts with non-standard events may not decode correctly
- Payment failure — x402 payment of 0.1 USDC not provided or rejected

## How this service works

Decodes on-chain event data into structured fields. Submit raw event logs to receive human-readable decoded output.

## Output

Returns the event name (e.g. 'Transfer'), the full event signature (e.g. 'Transfer(address,address,uint256)'), the event signature hash, decoded argument key-value pairs (e.g. from/to/value), raw topics, topic count, match source (e.g. 'known_events'), raw data, and response time in milliseconds.

## Example request

```json
{
 "log_data": "0x0000000000000000000000000000000000000000000000000000000000001000",
 "log_topics": [
  "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
  "0x0000000000000000000000001111111111111111111111111111111111111111",
  "0x0000000000000000000000002222222222222222222222222222222222222222"
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-shield-hazel-vercel-app-4105a385/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from defi-shield-hazel.vercel.app](https://www.zero.xyz/host/defi-shield-hazel.vercel.app/llms.txt)