# Phantom API — Metis Transaction History

> Phantom API — Metis 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 on the Metis blockchain network for specified addresses, blocks, and categories

## Facts

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

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-metis-transaction-history-db74e699 -d '<json body>'
```

Example prompt: Pull the last 25 transactions to the Metis wallet address 0xAbC...123, sorted newest first, including full metadata, and skip any zero-value transfers.

## When to prefer this

Choose this endpoint when you need transaction history specifically on the Metis Layer 2 network and want fine-grained filtering by address, block range, category, and sort order. Prefer it over generic Ethereum mainnet history APIs when your use case targets Metis. It supports pagination for large result sets and optional rich metadata, making it suitable for audit, analytics, and wallet activity monitoring workflows.

## Known failure modes

- Invalid address format returns a 400 bad request error
- Unrecognized category filter values may return empty results or an error
- pageKey expiry or mismatch causes pagination to fail
- Exceeding maxCount limits may truncate results
- Payment failure (insufficient USDC balance) results in a 402 Payment Required response
- Requests for blocks beyond the chain tip may return no 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

A paginated list of transactions on the Metis network matching the specified address(es), block range, and category filters. Each entry includes transaction details such as sender, recipient, block number, value, and optionally full metadata. A pageKey is returned 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-metis-transaction-history-db74e699/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)