# Pocket Network Event Log Decoding

> Pocket Network Event Log Decoding is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Decodes EVM smart contract event logs for a given transaction hash and chain ID into human-readable form.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/event-log-decoding?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-event-log-decoding-623bf689
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EZnPt9m2Ej5rVHR3KRjwR

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 pocket-network-event-log-decoding-623bf689 -d '<json body>'
```

Example prompt: Can you decode the event logs for Ethereum mainnet transaction 0x4a2b7c8e9f1d3e5a6b8c0d2e4f6a8b0c2d4e6f8a0b2c4d6e8f0a2b4c6d8e0f2a — what events were emitted?

## When to prefer this

Choose this endpoint when you need to decode EVM event logs from a specific transaction without managing API keys or account registration. It is ideal for pay-per-call, ad-hoc blockchain data needs where you want decoded event semantics rather than raw hex log data. Prefer this over setting up a full Ethereum node or subscribing to an indexer service when you only need occasional transaction-level event decoding on demand.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on the specified chain returns empty or error response
- Unsupported chain ID returns an error or unrecognized chain response
- Transaction exists but has no event logs returns empty data object
- Network or upstream Pocket Network node unavailability causes timeout or 5xx error

## How this service works

Pay-per-call access to Pocket Network services. No account, no API key.

## Output

Returns a JSON object with decoded event log data from the specified transaction, along with portal metadata including service ID, data provenance, and schema check status. The decoded events translate raw EVM log topics and data into structured, human-readable fields corresponding to the emitted Solidity events.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx_hash": {
   "type": "string",
   "description": "0x-prefixed transaction hash."
  },
  "chain_id": {
   "type": "integer",
   "description": "EVM chain id (1 for Ethereum mainnet)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "portal": {
   "serviceId": "event-log-decoding",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-event-log-decoding-623bf689/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)