# EVM Transaction Status & Decoded Transfer Lookup

> EVM Transaction Status & Decoded Transfer Lookup is a paid API for AI agents from api.agent-data.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-14).

Returns the status, confirmations, fee, and decoded ERC-20 transfers for an EVM transaction hash, searching across all chains if none specified.

## Facts

- Endpoint: GET https://api.agent-data.workers.dev/api/v1/evm/tx?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-status-decoded-transfer-lookup-7b5f8611
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S29fvXeKwx2xBAcYOupdE

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 evm-transaction-status-decoded-transfer-lookup-7b5f8611
```

Example prompt: Can you check if the transaction 0x4a3f...d92e went through on Base — I need to know if it succeeded, how many confirmations it has, and whether the USDC transfer actually landed?

## When to prefer this

Use this endpoint when you need to verify that an on-chain EVM payment actually arrived and settled, decode which ERC-20 tokens were transferred, or check confirmation depth across multiple chains without knowing which chain the tx is on. Prefer this over a block explorer when you need machine-readable structured data for agent decision-making, especially for payment verification workflows.

## Known failure modes

- Transaction hash not found on any chain — returns not found or null result
- Invalid or malformed 0x hash format causes a 400 error
- Transaction is still pending with zero confirmations
- Chain name typo causes search to fail or fall back to all-chain search
- Very new transactions may not yet be indexed

## How this service works

Status of an EVM transaction (pending, success, failed), confirmations, time, fee and decoded ERC-20 transfers; searches all chains if none given. Use to verify a payment arrived.

## Output

A JSON object containing the chain the transaction was found on, its status (pending, success, or failed), number of confirmations, timestamp, fee in native token, and an array of decoded ERC-20 token transfers each with recipient address, amount, and token symbol.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "0x transaction hash"
      },
      "chain": {
       "type": "string",
       "description": "Optional chain name"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "fee": 0.0000021,
  "chain": "base",
  "status": "success",
  "confirmations": 12,
  "token_transfers": [
   {
    "to": "0x2a99...",
    "amount": 0.005,
    "symbol": "USDC"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-status-decoded-transfer-lookup-7b5f8611/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agent-data.workers.dev](https://www.zero.xyz/host/api.agent-data.workers.dev/llms.txt)
