# Phantom API — ApeChain Transaction History

> Phantom API — ApeChain 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 ApeChain network for given addresses and block ranges

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/apechain/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-apechain-transaction-history-00be3a5e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QSSLc2dgHf79tQMm-BAvT

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-apechain-transaction-history-00be3a5e -d '<json body>'
```

Example prompt: Pull the last 25 transactions sent from ApeChain address 0xABC...123 in descending order, including metadata, and exclude any zero-value transfers.

## When to prefer this

Choose this endpoint when you need fast, paginated, filterable transaction history specifically on the ApeChain network. It supports rich filtering by address direction, block range, transaction category, zero-value exclusion, and sort order, making it ideal for wallet auditing, accounting, or monitoring use cases. Prefer this over generic block explorers when you need structured JSON output compatible with agent workflows and pay-per-call pricing without subscription overhead.

## Known failure modes

- Invalid or missing address format returns a 400 error
- Invalid block range (toBlock < fromBlock) may return empty results or an error
- Exceeded maxCount limit may result in truncated response with a pageKey for continuation
- Network congestion or node unavailability may cause timeout or 503 error
- Invalid pageKey returns an error or restarts pagination
- Payment not fulfilled results in 402 Payment Required response

## 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 for the specified ApeChain addresses and block range, including transfer details, asset category, block number, transaction hash, and optionally enriched metadata. A pageKey is provided when more results are available.

## 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-apechain-transaction-history-00be3a5e/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)