# Phantom API — BOB Transaction History

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

Retrieves paginated on-chain transaction history for the BOB (Build on Bitcoin) network, filtered by address, block range, category, and other parameters.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/bob/tx/history?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-bob-transaction-history-e424c682
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x2dqMJxZgmt09tCdH7oRq

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-bob-transaction-history-e424c682 -d '<json body>'
```

Example prompt: Pull the last 25 transactions (descending order) for wallet address 0xAbC123... on BOB network, including metadata, and skip zero-value transfers.

## When to prefer this

Use this endpoint when you need historical transaction data specifically on the BOB (Build on Bitcoin) network with fine-grained filtering by address, block range, category, and sort order. It is ideal for auditing wallet activity, building transaction explorers, or powering DeFi dashboards on BOB. Prefer this over generic Ethereum history endpoints when targeting BOB specifically, and over block explorers when you need structured, machine-readable paginated output.

## Known failure modes

- Invalid address format returns a 400 error
- Unknown or unsupported category value causes a validation error
- Invalid block number format (non-hex or non-numeric) returns an error
- Page key expired or invalid causes pagination failure
- Rate limits or payment failures (x402) return 402 Payment Required
- Network downtime or indexer lag may return empty or stale results

## 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 BOB network matching the specified filters, including optional metadata such as token details, block timestamps, and asset values. Also returns 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-bob-transaction-history-e424c682/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)