Transaction Decoding

blockchain

Serving

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.

Endpoint: POST https://agent.pocket.network/v1/tx-decoding/v1/tool
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/tx-decoding/v1/tool \
  -H 'content-type: application/json' \
  -d '{"arguments":{"tx_hash":"0xe1b34f8c48b70d9828b191e7eebf08b27601f6122692357975c9229d0af10575","chain_id":"1"}}'

Example response

The response this call returned, captured 2026-09-21 23:49:53 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "tx-decoding",
    "schemaCheck": "unchecked"
  },
  "data": {
    "abi_source": "live_tx_fetch",
    "as_of": "2026-09-21T23:49:52Z",
    "candidates": [],
    "chain": "ethereum",
    "chain_id": 1,
    "confidence": "high",
    "decoded_args": {
      "amount": "100000000",
      "to": "0x6928f3e126dbac9923d52300fdef714b280b305c"
    },
    "erc20_transfer": {
      "amount_raw": "100000000",
      "to": "0x6928f3e126dbac9923d52300fdef714b280b305c"
    },
    "function": "transfer",
    "human_summary": "Token transfer call on ethereum: transfer(recipient=0x6928f3e126dbac9923d52300fdef714b280b305c, amount_raw=100000000)",
    "selector": "0xa9059cbb",
    "signature": "transfer(address,uint256)",
    "to": "0xdac17f958d2ee523a2206206994597c13d831ec7",
    "value_wei": "0"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Transaction Decoding accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/evm`	read
`POST /v1/tool`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "A transaction or calldata to decode. On the MCP relay route POST /v1/tool these fields are wrapped under an `arguments` object; the direct route takes them at the top level.",
  "properties": {
    "tx_hash": {
      "type": "string",
      "description": "The transaction hash, 0x-prefixed."
    },
    "chain_id": {
      "type": "integer",
      "description": "EVM chain id (default 1)."
    }
  },
  "required": [
    "tx_hash"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/evm, a JSON object with the decoded function signature, arguments, ERC-20 transfers, and the chain_id. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}