# Phantom API — Plasma Transaction History

> Phantom API — Plasma 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-16).

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

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/plasma/tx/history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-plasma-transaction-history-555d3bf6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Gbgx4Jn_m7lV-Ac-pVXPC

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-plasma-transaction-history-555d3bf6 -d '<json body>'
```

Example prompt: Pull the last 25 on-chain transactions sent from 0xABC...123 to 0xDEF...456 in descending order, including metadata, and skip any zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical on-chain transaction data for a specific wallet or contract address, especially when you need filtering by block range, category, or direction. It is particularly suited for auditing wallet activity, monitoring incoming payments, or building transaction histories for DeFi analytics. Prefer this over generic RPC calls (e.g., eth_getTransactionByHash) when you need multi-transaction queries with metadata enrichment and pagination support.

## Known failure modes

- Invalid or malformed address returns a 400 error
- fromBlock or toBlock values outside available indexed range may return empty results
- Exceeding maxCount limits may truncate results without warning
- Missing required address fields results in a validation error
- Network congestion or indexer lag may cause stale or incomplete data
- Payment failure (x402) blocks the request entirely

## 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 on-chain transactions matching the specified address(es), block range, and category filters. Each transaction record typically includes block number, transaction hash, 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-plasma-transaction-history-555d3bf6/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)