# Phantom API — Arbitrum Transaction History

> Phantom API — Arbitrum Transaction History is a paid API for AI agents from phantom-api-omega.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Retrieves paginated transaction history on the Arbitrum network for a given address or address pair, with optional block range filtering and metadata enrichment.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/arbitrum/tx/history?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-arbitrum-transaction-history-eeb2c8fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Tx48RNwDuH8X4X_bHa7W-

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 phantom-api-arbitrum-transaction-history-eeb2c8fa -d '<json body>'
```

Example prompt: Pull the last 100 transactions on Arbitrum for wallet 0xAbC...123 going from most recent to oldest, include token metadata, and skip zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical transaction or asset transfer data specifically on the Arbitrum L2 network, with support for block-range filtering, pagination, category filtering (ERC-20, ERC-721, internal, external), and metadata enrichment. Prefer this over generic block explorers when you need structured, machine-readable data for agent workflows or on-chain auditing.

## Known failure modes

- Invalid or missing address returns empty result or 400 error
- Invalid block range (fromBlock > toBlock) returns error
- Unrecognized category values may be ignored or return 400
- pageKey from a different query context causes unexpected results
- Rate limiting or payment failure returns 402
- Arbitrum node unavailability returns 503 or timeout

## How this service works

Lightning-fast access to blockchain data, smart contract insights, and Web3 infrastructure across 57+ networks. Pay-per-call via x402.

## Output

Returns a paginated list of asset transfers and transactions on the Arbitrum network, including transaction hashes, block numbers, asset categories (ERC-20, ERC-721, internal, external, etc.), token metadata (symbol, decimals, name), from/to addresses, values, and a pageKey for continued pagination.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "order": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "pageKey": {
   "type": "string"
  },
  "toBlock": {
   "type": "string"
  },
  "category": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "maxCount": {
   "type": "number"
  },
  "fromBlock": {
   "type": "string"
  },
  "toAddress": {
   "type": "string"
  },
  "fromAddress": {
   "type": "string"
  },
  "withMetadata": {
   "type": "boolean"
  },
  "excludeZeroValue": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-arbitrum-transaction-history-eeb2c8fa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phantom-api-omega.vercel.app](https://www.zero.xyz/host/phantom-api-omega.vercel.app/llms.txt)