# Phantom API — On-Chain Transaction History

> Phantom API — On-Chain 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-09-13).

Retrieves paginated blockchain transaction history for a given address or address pair across 57+ networks, with optional metadata and category filters.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/tempo/tx/history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-on-chain-transaction-history-5eecaa33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1Qv5nWB8Sc1AZl8ge1OLr

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-on-chain-transaction-history-5eecaa33 -d '<json body>'
```

Example prompt: Pull the last 50 transactions sent from wallet 0xABC123 up to block 19000000, include metadata, and sort them in descending order so I can see the most recent ones first.

## When to prefer this

Use this endpoint when you need historical on-chain transaction data for a specific wallet or contract address, especially when you require pagination, block-range filtering, or category-based filtering (e.g. ERC20, internal, external). Prefer this over real-time event streaming endpoints when doing historical analysis or auditing. Suitable for pay-per-call usage where you only need occasional lookups rather than a subscription.

## Known failure modes

- Invalid address format returns a 400 error
- Unsupported category values cause a validation error
- Block range too large may result in timeout or truncated results
- Missing fromAddress or toAddress with no filter may return empty results
- pageKey from a different query context causes pagination errors
- Network unavailable or node timeout returns 5xx

## 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 on-chain transactions matching the specified address(es), block range, and category filters. Each record typically includes transaction hash, block number, from/to addresses, value, asset type, and optional metadata. A pageKey is included when more results are available.

## 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-on-chain-transaction-history-5eecaa33/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)