# Phantom API — Humanity Token Transfers

> Phantom API — Humanity Token Transfers 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 token transfer history for a given wallet address on the Humanity protocol, with filtering by block range and contract address.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/humanity/token/transfers?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-humanity-token-transfers-f8576ece
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HlzALO8dVmjKsSjUrIMp_

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-humanity-token-transfers-f8576ece -d '<json body>'
```

Example prompt: Pull all token transfers for wallet 0xAbC123... on the Humanity network, sorted newest first, for up to 50 results — filter to just the contract at 0xDEF456... between block 1000000 and 2000000.

## When to prefer this

Use this endpoint when you need on-chain token transfer history specifically within the Humanity protocol ecosystem across 57+ supported networks, and need block-range filtering, contract-level filtering, and cursor-based pagination — particularly when paying per-call via x402 is acceptable and you need fast indexed results rather than running a full node query.

## Known failure modes

- Invalid wallet address format returns an error or empty result
- Invalid block range (toBlock < fromBlock) may return an error
- Unknown or unsupported contract address yields empty transfers array
- Missing required owner field causes a 400 bad request
- Expired or invalid pageKey causes pagination failure
- Rate limiting or payment failure (402) if USDC payment not processed

## 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 token transfer records for the specified owner address, including transaction hashes, block numbers, token contract addresses, amounts, sender/receiver addresses, and a pagination key for fetching subsequent pages.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "order": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "owner": {
   "type": "string"
  },
  "pageKey": {
   "type": "string"
  },
  "toBlock": {
   "type": "string"
  },
  "maxCount": {
   "type": "number"
  },
  "fromBlock": {
   "type": "string"
  },
  "contractAddresses": {
   "type": "array",
   "items": {
    "type": "string"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-humanity-token-transfers-f8576ece/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)