# Phantom API — Polygon NFT Metadata Lookup

> Phantom API — Polygon NFT Metadata Lookup 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).

Fetches on-chain NFT metadata for a given contract address and token ID on the Polygon network

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/polygon/nft/metadata
- 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-metadata-lookup-63cb8349
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9yFviyDG28rT7RRmZDQSp

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-metadata-lookup-63cb8349 -d '<json body>'
```

Example prompt: Can you pull up the metadata for token ID 1234 from the Polygon NFT contract at address 0xAbCd1234...? I want to see its name, description, image, and any traits.

## When to prefer this

Choose this endpoint when you specifically need NFT metadata from the Polygon (MATIC) network and want a pay-per-call model without committing to a subscription. It is ideal for agents that need fast, on-demand lookups of individual NFT tokens by contract address and token ID, especially when building workflows that check traits, display collectibles, or verify metadata before a transaction.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty response
- Token ID not found on the contract returns a 404 or null metadata
- Contract does not implement standard metadata URI function — returns an error
- Polygon RPC node unavailable — returns a timeout or 503
- Malformed input (non-hex contract address, non-numeric token ID) returns a 400 validation error
- IPFS or off-chain metadata URI unreachable — may return partial or no metadata

## 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 on-chain NFT metadata for the specified Polygon token, typically including the token name, description, image URI, external URL, and an array of trait/attribute key-value pairs as defined by the NFT contract's metadata standard (ERC-721/ERC-1155).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokenId": {
   "type": "string"
  },
  "contractAddress": {
   "type": "string"
  }
 }
}
```

## More

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