# Phantom API — BNB Chain Transaction History

> Phantom API — BNB Chain 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-15).

Retrieves paginated transaction history for addresses on the BNB (Binance Smart Chain) network, with filtering by block range, address, category, and metadata options.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/bnb/tx/history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-bnb-chain-transaction-history-20a999e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7qzvz5D_RHkyPIn2PmL3_

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-bnb-chain-transaction-history-20a999e9 -d '<json body>'
```

Example prompt: Pull the last 50 BNB Chain transactions sent from wallet 0xABC...123, ordered from newest to oldest, and include metadata — skip any zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical transaction data specifically on the BNB (Binance Smart Chain) network, with flexible filtering by address, block range, and category. It is particularly suited for agents needing paginated, pay-per-call access to on-chain BNB activity without managing node infrastructure. Prefer this over Ethereum or multi-chain endpoints when the target chain is explicitly BNB.

## Known failure modes

- Invalid address format returns an error or empty results
- fromBlock/toBlock out of range or non-existent returns empty list
- Unsupported category value causes validation error
- maxCount exceeding API limits may be clamped or rejected
- Missing required address fields may return all transactions (potentially large payload)
- Network downtime on BNB Chain node causes 5xx errors
- Payment failure via x402 protocol blocks request

## 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 BNB Chain transactions matching the specified filters, including sender/receiver addresses, block numbers, transaction categories, optional metadata (e.g. token decimals, asset names), and a pageKey for fetching subsequent pages.

## 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-bnb-chain-transaction-history-20a999e9/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)