# Phantom API — Polygon NFT Sales

> Phantom API — Polygon NFT Sales 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 historical NFT sales transactions on the Polygon blockchain, filterable by contract address and block range.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/polygon/nft/sales
- 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-polygon-nft-sales-2c3da656
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tS3LWzsbUuq68sJ9hXP_T

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-polygon-nft-sales-2c3da656 -d '<json body>'
```

Example prompt: Pull the last 50 NFT sales on Polygon for the contract address 0xA1b2C3d4E5f6... ordered from newest to oldest — I want to see what's been trading recently.

## When to prefer this

Choose this endpoint when you need on-chain NFT sales data specifically from the Polygon network and want block-level precision over the query range. It is ideal for agents that need historical trade data for a specific contract without relying on third-party NFT marketplace APIs. Prefer it over general blockchain explorers when pay-per-call cost efficiency matters and you need programmatic, structured sales records.

## Known failure modes

- Invalid or non-checksum contract address returns an error or empty result
- fromBlock greater than toBlock yields no results or a validation error
- Block range too large may cause timeout or truncated results
- Payment failure (x402) blocks the request if USDC balance is insufficient
- Network unavailability on Phantom API infrastructure returns a 5xx error

## 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

An array of NFT sale events on the Polygon network, each containing transaction details such as sale price, token ID, buyer/seller addresses, and block number, scoped to the specified contract address and block range.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "number"
  },
  "order": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "toBlock": {
   "type": "number"
  },
  "fromBlock": {
   "type": "number"
  },
  "contractAddress": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-polygon-nft-sales-2c3da656/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)