# Phantom API — X Layer Transaction History

> Phantom API — X Layer 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 for addresses on the X Layer (XLayer) blockchain network

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/xlayer/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-x-layer-transaction-history-4ccc7422
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wmWg6ynzYIdDqu36xB4sZ

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-x-layer-transaction-history-4ccc7422 -d '<json body>'
```

Example prompt: Pull the last 25 transactions for wallet address 0xAbC123... on X Layer, sorted newest first, including metadata and excluding zero-value transfers.

## When to prefer this

Use this endpoint when you need paginated, filterable transaction history specifically on the X Layer (XLayer) network. It supports fine-grained filtering by sender/receiver address, block range, transaction category, and zero-value exclusion, making it ideal for wallet audits, portfolio reconciliation, or DeFi analytics on XLayer. Prefer this over generic block explorers when you need structured, machine-readable JSON output compatible with agent pipelines and pay-per-call economics via x402.

## Known failure modes

- Invalid address format returns a 400 bad request error
- Specifying an out-of-range block returns empty results or an error
- Invalid category values result in a validation error
- Exceeding maxCount limits may return a truncated result or error
- Expired or invalid pageKey causes pagination to restart or fail
- Network unavailability returns a 5xx server error
- Insufficient payment (x402) results in a 402 Payment Required response

## 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 the X Layer network matching the specified address filters, block range, and category criteria. Each transaction entry typically includes the transaction hash, block number, from/to addresses, asset type, value, and optional metadata. A pageKey is returned when more results are available for subsequent pagination 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-x-layer-transaction-history-4ccc7422/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)