# Pocket Network EVM Transaction Decoder

> Pocket Network EVM Transaction Decoder 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 raw EVM transaction hashes into human-readable function signatures, decoded arguments, and ERC-20 transfer details

## Facts

- Endpoint: POST https://agent.pocket.network/v1/tx-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-evm-transaction-decoder-c8b9e709
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G5Q2VtBAhkfMCi-XsPlIQ

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-evm-transaction-decoder-c8b9e709 -d '<json body>'
```

Example prompt: Can you decode this Ethereum transaction for me — 0x4a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789ab on chain ID 1 — and tell me what function was called, what arguments were passed, and if any ERC-20 tokens were transferred?

## When to prefer this

Choose this endpoint when an agent needs to understand the semantic intent of an EVM transaction — what function was called and with what arguments — without setting up a full node or managing API keys. It is especially useful for DeFi monitoring, transaction auditing, wallet activity summarization, and compliance workflows. Prefer this over raw JSON-RPC eth_getTransaction calls when human-readable decoded output is needed immediately, and over block explorers when programmatic JSON output is required for downstream processing.

## Known failure modes

- Transaction hash not found on the specified chain — returns error if the tx does not exist or hasn't been indexed yet
- Invalid or malformed tx_hash format — returns validation error for non-0x-prefixed or wrong-length hashes
- Unsupported chain_id — returns error if the requested EVM chain is not supported by Pocket Network
- Unverified contract ABI — function selector may be decoded with best-guess ABI if not publicly verified, resulting in partial or generic output
- Payment failure — request rejected if USDC payment via x402 protocol is not successfully attached

## How this service works

Decodes raw EVM transactions and calldata into agent-readable intent: function signature, decoded arguments, and ERC-20 transfers. POST /v1/evm with {tx_hash, chain_id} and get one JSON object back. Fully deterministic: input determines output. Pay per request in USDC; no account, no API key.

## Output

A single JSON object containing the decoded function signature (name and parameter types), the decoded argument values mapped to their parameter names, and a list of any ERC-20 token transfer events detected within the transaction, making the on-chain intent fully human- and agent-readable.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-evm-transaction-decoder-c8b9e709/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)