{"slug":"agent-pocket-network-v1-tx-explain-ed9f08","title":"Explains an EVM transaction in plain language","host":"agent.pocket.network","method":"POST","resource":"https://agent.pocket.network/v1/tx-explain","category":"other","description":"Explains an EVM transaction in plain language: decoded intent, asset movements, approvals, and risk flags. POST /v1/tool with {tx_hash, chain_id}, or GET /v1/explain with query params, and get one JSON object with a summary, moved assets, gas, parties, and risk flags. Deterministic for identical inp","price_listed":0.005,"price_asked":0.005,"state":"answering","state_label":"Answering","checks_7d":1,"answered_7d":1,"latency_ms_median":1002,"reported_calls_30d":6,"reported_payers_30d":2,"networks":["eip155:8453"],"badge":"unverified","paid_checks_7d":0,"paid_ok_7d":0,"example_input":{"body":{"tx_hash":""},"bodyType":"json","method":"POST","type":"http"},"output_schema":{"$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"input":{"additionalProperties":false,"properties":{"body":{"description":"A transaction to explain. 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. GET /v1/explain takes the same fields as query parameters.","properties":{"chain_id":{"description":"EVM chain id (default 1).","type":"integer"},"tx_hash":{"description":"The transaction hash, 0x-prefixed.","type":"string"}},"required":["tx_hash"],"type":"object"},"bodyType":{"enum":["json","form-data","text"],"type":"string"},"method":{"enum":["POST","PUT","PATCH"],"type":"string"},"type":{"const":"http","type":"string"}},"required":["type","method","bodyType","body"],"type":"object"},"output":{"properties":{"example":{"properties":{"data":{"description":"For POST /v1/tool (and GET /v1/explain), a JSON object with a plain-language summary, moved assets, gas, parties, risk flags, and the chain_id as received. 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.","type":"object"},"portal":{"properties":{"provenance":{"const":"third-party-supplier"},"schemaCheck":{"enum":["passed","undeclared","unchecked"]},"serviceId":{"const":"tx-explain"}},"required":["provenance","serviceId","schemaCheck"],"type":"object"}},"required":["portal","data"],"type":"object"},"type":{"type":"string"}},"required":["type"],"type":"object"}},"required":["input"],"type":"object"},"history":[{"day":"2026-09-24","reachable":true,"status":402,"valid_402":true,"asked_usdc":0.005,"price_match":true,"latency_ms":1002,"error":null}],"description_full":"Explains an EVM transaction in plain language: decoded intent, asset movements, approvals, and risk flags. POST /v1/tool with {tx_hash, chain_id}, or GET /v1/explain with query params, and get one JSON object with a summary, moved assets, gas, parties, and risk flags. Deterministic for identical input. Pay per request in USDC; no account, no API key.","last_updated":"2026-09-24T04:30:28.918Z","schemes":["exact"]}