# Phantom API — Sonic Transaction History

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

Retrieves paginated transaction history on the Sonic blockchain network, filtered by address, block range, category, and other criteria

## Facts

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

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-sonic-transaction-history-728b60e1 -d '<json body>'
```

Example prompt: Pull the last 25 transactions sent from wallet 0xAbC123... on the Sonic network, sorted newest first, and include metadata — skip any zero-value transfers.

## When to prefer this

Use this endpoint when you need historical transaction data specifically on the Sonic blockchain network, with flexible filtering by address, block range, and category. Prefer this over general EVM history APIs when the target chain is Sonic and you need pay-per-call pricing without a subscription.

## Known failure modes

- Invalid or missing address formats return an error response
- Unsupported block range or out-of-bounds blocks may return empty results or an error
- Invalid category values may cause a 400 bad request
- Exceeding maxCount limits or passing an invalid pageKey may cause pagination errors
- Payment failure via x402 protocol results in a 402 response blocking data access

## 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 transaction records on the Sonic blockchain matching the specified filters, potentially including metadata such as token details, block numbers, timestamps, sender/receiver addresses, and a pageKey for continuation.

## 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-sonic-transaction-history-728b60e1/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)
