# Phantom API — opBNB Transaction History

> Phantom API — opBNB 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 transaction history for addresses on the opBNB blockchain network

## Facts

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

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-opbnb-transaction-history-b8c24045 -d '<json body>'
```

Example prompt: Pull the last 50 transactions for opBNB address 0xABC...123, sorted descending by block, and include metadata — skip any zero-value transfers.

## When to prefer this

Use this endpoint when you need historical transaction data specifically on the opBNB (Optimistic BNB) Layer-2 network. Prefer it over generic explorers when you need programmatic, paginated, filterable access to wallet or contract transaction history with metadata, block-range filters, and sort control — especially in agent workflows that process on-chain activity automatically via pay-per-call access.

## Known failure modes

- Invalid address format returns a 400 error
- Invalid block range (toBlock less than fromBlock) causes an error
- Unknown category values may be rejected or silently ignored
- Exceeding maxCount limits may result in truncated results or errors
- Network downtime or RPC issues may return 500 errors
- Expired or invalid x402 payment token causes a 402 payment required error

## 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 on the opBNB network, including sender/receiver addresses, block numbers, transaction hashes, asset transfer details, and optionally metadata. A pageKey is included when more results are available for the next page.

## 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-opbnb-transaction-history-b8c24045/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)