# Zora NFT Metadata Lookup

> Zora 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-10-18).

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

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/zora/nft/metadata?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zora-nft-metadata-lookup-fc4ddeae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RUlL4K4FAdvpBYY9aVB7F

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 zora-nft-metadata-lookup-fc4ddeae -d '<json body>'
```

Example prompt: Can you pull the on-chain metadata for Zora NFT contract 0x1234...abcd, token ID 42 — I want to see the name, description, image, and any attributes stored on-chain.

## When to prefer this

Choose this endpoint when you need fast, pay-per-call NFT metadata retrieval specifically from the Zora network without managing your own RPC node or indexer. It is ideal for lightweight, on-demand lookups where you know the contract address and token ID and want structured metadata back immediately. Prefer it over general-purpose blockchain RPCs when you want a simple HTTP interface rather than raw eth_call interactions.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty response
- Token ID not found on the specified contract returns a not-found error
- Network or RPC timeout causes a slow or failed response
- Malformed contractAddress or tokenId input triggers a validation error
- IPFS-hosted metadata may be slow or unavailable if the gateway is down
- Payment failure via x402 protocol blocks the request before it reaches the chain

## 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 Zora token, typically including the token name, description, image URL, external URL, and any traits or attributes defined in the token's metadata JSON stored on-chain or via IPFS.

## 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/zora-nft-metadata-lookup-fc4ddeae/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)