# Phantom API – opBNB NFT Metadata Lookup

> Phantom API – opBNB 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 (name, image, traits, etc.) for a given token on the opBNB network by contract address and token ID.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/opbnb/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/phantom-api-opbnb-nft-metadata-lookup-2c9c38da
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tfta0KP4r4-E1E7NwLNXd

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-opbnb-nft-metadata-lookup-2c9c38da -d '<json body>'
```

Example prompt: Can you pull up the metadata for the opBNB NFT at contract address 0xAbC...123 with token ID 42 — I want to see its name, image, and traits?

## When to prefer this

Choose this endpoint when you need NFT metadata specifically on the opBNB (optimistic BNB) Layer-2 network and want fast, pay-per-call access without managing your own RPC infrastructure. Prefer it over general-purpose blockchain RPC calls when you want a simple POST interface abstracting away the raw contract interaction, and over competing indexers when you only need individual token lookups rather than bulk collection queries.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty response
- Token ID does not exist on the contract (unminted or burned) returns a not-found error
- Contract does not implement a standard metadata URI function — metadata may be unavailable
- opBNB RPC node downtime or congestion may cause timeouts
- Malformed input (wrong address format) returns a validation error
- IPFS or off-chain metadata URI is unreachable, causing partial or null response

## 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 NFT metadata for the specified opBNB token, typically including the token name, description, image URI, and an array of attributes/traits as defined by the smart contract's token URI standard (ERC-721/ERC-1155 metadata JSON).

## 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-opbnb-nft-metadata-lookup-2c9c38da/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)