# Phantom API — Boba Network Transaction History

> Phantom API — Boba Network 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 Boba Network blockchain, with filtering by block range, category, and address.

## Facts

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

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-boba-network-transaction-history-d408888a -d '<json body>'
```

Example prompt: Pull the last 25 transactions sent from 0xAbC...123 on Boba Network, sorted in descending order, and include metadata — skip any zero-value transfers.

## When to prefer this

Use this endpoint when you need historical transaction data specifically on the Boba Network (L2) and want flexible filtering by address, block range, category, and ordering — especially when pay-per-call pricing at $0.01 USDC per query is preferable to maintaining your own indexer subscription.

## Known failure modes

- Invalid address format returns a 400 error
- fromBlock greater than toBlock returns empty result or error
- Invalid category value causes query rejection
- maxCount exceeding API limits may return partial results or error
- Payment failure (x402) blocks the request before execution
- Network downtime or Boba RPC issues cause 500 errors

## 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 Boba Network matching the specified filters, including block numbers, transaction hashes, sender/receiver addresses, asset categories, and optional metadata. A pageKey is provided 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-boba-network-transaction-history-d408888a/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)