# Phantom API — Blockchain Transaction History

> Phantom API — Blockchain 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-14).

Retrieves paginated on-chain transaction history for a given address or block range across 57+ blockchain networks

## Facts

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

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-blockchain-transaction-history-0f5aeef4 -d '<json body>'
```

Example prompt: Pull the last 25 incoming transactions to wallet address 0xABC...123, ordered from newest to oldest, and include full metadata — skip any zero-value transfers.

## When to prefer this

Choose this endpoint when you need fast, paginated, filterable on-chain transaction history for a specific wallet or contract address, especially across 57+ supported networks. It is ideal when you want server-side filtering by category, block range, or zero-value exclusion rather than pulling raw block data. Prefer this over general RPC calls when you need structured, ready-to-use transaction records with optional metadata enrichment.

## Known failure modes

- Invalid or malformed address formats return an error
- Unsupported network or block range out of bounds may return empty results
- Missing required address parameters cause validation errors
- Expired or invalid pageKey breaks pagination continuity
- Rate limits or payment failures (x402) result in 402 Payment Required responses
- Large maxCount values or wide block ranges may time out or be truncated

## 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, block range, and category filters. Each record may include transaction hash, block number, sender, recipient, value, asset type, and optional metadata such as token name and decimals. A pageKey is included when additional pages 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-blockchain-transaction-history-0f5aeef4/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)