# Phantom API — Humanity Transaction History

> Phantom API — Humanity 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 on-chain transaction history for a given address or address pair across blockchain networks

## Facts

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

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-humanity-transaction-history-bbb27ff2 -d '<json body>'
```

Example prompt: Pull the last 25 transactions for wallet 0xABC...123, sorted newest first, including metadata and excluding zero-value transfers, starting from block 18000000.

## When to prefer this

Use this endpoint when you need historical on-chain transaction records for a specific address or address pair, especially when you require pagination, block-range filtering, category filtering (e.g. ERC20, internal, external), or metadata-enriched results. Prefer this over generic RPC calls when you want structured, queryable transaction history without parsing raw block data yourself. Well-suited for auditing, portfolio analysis, and compliance workflows.

## Known failure modes

- Invalid or malformed address returns a 400 error
- Block range too large may cause timeout or truncated results
- Invalid pageKey causes pagination error or restart
- Unsupported category value returns empty results or error
- Network unavailable returns 503 or gateway error
- Exceeding maxCount limits may return partial results

## 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 filters, block range, and category criteria. Each record includes transaction hash, block number, from/to addresses, value, asset, category, and optionally full metadata. A pageKey is returned when more results are available for 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-humanity-transaction-history-bbb27ff2/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)