# Phantom API — Ethereum Transaction History

> Phantom API — Ethereum 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 Ethereum transaction history for a given address or address pair, filterable by block range, category, and metadata options

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/ethereum/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-ethereum-transaction-history-36c7a675
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pKLIYbcWQk5Wy1NUte8W4

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-ethereum-transaction-history-36c7a675 -d '<json body>'
```

Example prompt: Pull the last 100 transactions for Ethereum address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045, sorted newest first, including metadata, and skip any zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical Ethereum transaction data with flexible filtering by address, block range, and asset category. It is well-suited for wallet auditing, portfolio analytics, tax reporting, and tracing on-chain fund flows. Prefer it over general block explorers when you need structured, machine-readable paginated output with metadata in a pay-per-call model without rate-limit subscription commitments.

## Known failure modes

- Invalid Ethereum address format returns a 400 error
- fromBlock greater than toBlock returns an empty result or error
- Invalid category values may return an error or be silently ignored
- Expired or invalid pageKey causes pagination to fail
- maxCount exceeding API limits may be capped or rejected
- Network errors or Vercel cold starts may cause timeouts
- Payment failure via x402 protocol blocks the request

## 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 Ethereum asset transfers and transactions matching the query, each including transaction hash, block number, from/to addresses, value, asset type, and optionally full metadata. Also returns a pageKey for cursor-based pagination through large result sets.

## 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-ethereum-transaction-history-36c7a675/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)