# Phantom API — Zora Transaction History

> Phantom API — Zora 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 transaction history on the Zora network for a given address or block range, filtered by category and metadata options.

## Facts

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

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-zora-transaction-history-d4ae99e9 -d '<json body>'
```

Example prompt: Pull the last 100 transactions on the Zora network for wallet address 0xAbC...123, sorted newest first, with full metadata and excluding zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical transaction data specifically on the Zora network, with fine-grained filtering by address, block range, category, and value. Prefer it over generic block explorers when you need structured, machine-readable output with metadata and pagination support for AI agent workflows, and you want pay-per-call pricing without a subscription.

## Known failure modes

- Invalid address format returns a validation error
- Block range too large may result in timeout or truncated results
- Invalid category string returns an error or empty results
- Missing required address fields may return an empty result set
- pageKey from a different query context causes pagination errors
- Rate limiting or payment failure returns 402 or 429 status

## 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

A paginated list of Zora network transactions matching the specified filters, optionally enriched with metadata such as token name, symbol, and decimals. Includes a pageKey for fetching subsequent pages, transaction hashes, block numbers, from/to addresses, asset categories, and transfer values.

## 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-zora-transaction-history-d4ae99e9/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)