# Phantom API – Worldchain Transaction History

> Phantom API – Worldchain 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-18).

Retrieves paginated transaction history for addresses on the Worldchain network, filterable by block range, category, and address.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/worldchain/tx/history?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-worldchain-transaction-history-051349cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DmrV7QpTN_1XKmNlXLIud

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-worldchain-transaction-history-051349cc -d '<json body>'
```

Example prompt: Pull the last 50 transactions received by Worldchain address 0xAbC...123, sorted newest first, including metadata and excluding zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical transaction data specifically on the Worldchain network, with support for flexible filtering by address, block range, and asset category. It is ideal for auditing wallet activity, reconciling transfers, or building transaction timelines. Prefer this over generic block explorers when you need structured, paginated JSON output consumable by an AI agent or automated workflow, and when pay-per-call pricing at $0.01 USDC is acceptable.

## Known failure modes

- Invalid address format returns a 400 error
- Block range too large may result in timeout or truncated results
- Unknown category values may be silently ignored or return empty results
- Missing required address fields may return all-network data or an error
- pageKey expiration causes pagination to restart from the beginning
- Payment failure via x402 results in a 402 response before data is returned

## 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 transactions on Worldchain matching the specified filters, including transaction hashes, block numbers, from/to addresses, asset values, and optionally rich metadata. A pageKey is returned when more results are available for subsequent calls.

## 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-worldchain-transaction-history-051349cc/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)