# Phantom API — Katana Transaction History

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

Fetches paginated transaction history for a given address or block range on the Katana network via Phantom's Web3 infrastructure

## Facts

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

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-katana-transaction-history-8ed47a43 -d '<json body>'
```

Example prompt: Pull the last 25 transactions sent from wallet 0xAbC...123 on the Katana network, sorted newest first, and include transaction metadata.

## When to prefer this

Use this endpoint when you need historical transaction data specifically on the Katana network, require pagination support for large result sets, need to filter by block range or transaction category, or want to audit wallet activity with optional metadata. Prefer this over generic blockchain explorers when you need programmatic, pay-per-call access integrated into an agent workflow.

## Known failure modes

- Invalid or malformed address returns an error or empty result
- Block range out of bounds returns an empty array
- Invalid category filter may return no results or an error
- Missing required address fields may cause a 400 bad request
- Payment failure via x402 results in a 402 response blocking data access
- Exceeding maxCount limits may truncate results silently

## 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 list of transaction records for the specified address or block range on the Katana network, including transaction hashes, block numbers, sender/receiver addresses, values, categories, and optional metadata. A pagination key is included for fetching subsequent pages when there are more results.

## 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-katana-transaction-history-8ed47a43/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)