# Phantom API — Abstract NFT Metadata Lookup

> Phantom API — Abstract 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-15).

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

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/abstract/nft/metadata
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-abstract-nft-metadata-lookup-68359eab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qva6kIJdBgfXyozdDAKXE

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-abstract-nft-metadata-lookup-68359eab -d '<json body>'
```

Example prompt: What's the metadata for token ID 42 on the NFT contract 0xAbCd1234...5678 on Abstract — I need the name, image, and any trait attributes it has.

## When to prefer this

Choose this endpoint when you need fast, pay-per-call NFT metadata retrieval on the Abstract network without managing RPC nodes or API keys. It is ideal for lightweight agent workflows that occasionally need NFT details rather than high-volume indexing.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty response
- Token ID not found or not yet minted returns a 404 or null metadata
- Network unavailability or RPC errors cause timeouts
- Malformed input (non-hex contract address, non-numeric token ID) causes validation errors
- Contract does not implement standard metadata interface (ERC-721/ERC-1155) may return 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 structured NFT metadata for the specified token, typically including the token name, description, image URI, and an array of trait/attribute key-value pairs sourced directly from the on-chain contract on the Abstract network.

## 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-abstract-nft-metadata-lookup-68359eab/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)