# Agent Data Tools: Arbitrum Transaction Lookup

> Agent Data Tools: Arbitrum Transaction Lookup is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-19).

Fetches on-chain transaction details for a given transaction hash on the Arbitrum One network

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/arb/tx?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-data-tools-arbitrum-transaction-lookup-21b37ec7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_F2W7upuQ663YZweXYuGqN

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 agent-data-tools-arbitrum-transaction-lookup-21b37ec7
```

Example prompt: Can you look up the Arbitrum transaction 0xf03682db039f7b1b72ddf4d17572738f142cf63ecb36c90afa570430ea9774c4 and tell me who sent it, who received it, and what function was called?

## When to prefer this

Use this endpoint when you specifically need to look up a transaction on the Arbitrum One network by its hash and require structured fields like sender, recipient, block, gas, nonce, value, and function selector. Prefer this over generic block explorers when operating in an automated agent context with micropayment-based access and no API key setup.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on Arbitrum returns a not-found error
- Network or RPC timeout may cause temporary failures
- Hash from a different chain (e.g. Ethereum mainnet) will not be found on Arbitrum

## How this service works

Look up an Arbitrum One transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block. Use to see what was sent or whether it exists; for success or failure and fees paid use arb_receipt, for emitted events arb_logs. Input is a 0x-prefixed 64-hex hash; an unknown hash returns 404, uncharged.

## Output

A JSON object containing the transaction hash, sender address (from), recipient address (to), block number, chain name ('Arbitrum One'), chain ID (42161), gas, nonce, ETH value, 4-byte function selector, and count of input bytes.

## 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",
       "pattern": "^0x[0-9a-fA-F]{64}$",
       "examples": [
        "0xf03682db039f7b1b72ddf4d17572738f142cf63ecb36c90afa570430ea9774c4"
       ],
       "description": "0x-prefixed transaction hash (64 hex characters)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "to": {
       "type": "string"
      },
      "gas": {
       "type": "string"
      },
      "from": {
       "type": "string"
      },
      "hash": {
       "type": "string"
      },
      "block": {
       "type": "number"
      },
      "chain": {
       "type": "string"
      },
      "nonce": {
       "type": "number"
      },
      "value": {
       "type": "string"
      },
      "chainId": {
       "type": "number"
      },
      "selector": {
       "type": "string"
      },
      "inputBytes": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x…",
  "gas": "65000",
  "from": "0x…",
  "hash": "0xf03682db039f7b1b72ddf4d17572738f142cf63ecb36c90afa570430ea9774c4",
  "block": 123456789,
  "chain": "Arbitrum One",
  "nonce": 12,
  "value": "0.0",
  "chainId": 42161,
  "selector": "0xa9059cbb",
  "inputBytes": 68
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-data-tools-arbitrum-transaction-lookup-21b37ec7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)