# NFT Metadata Resolver

> NFT Metadata Resolver is a paid API for AI agents from agent402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Fetches display metadata for a single NFT by contract address and token ID, returning title, description, image URLs, traits, and token standard (ERC-721/ERC-1155)

## Facts

- Endpoint: POST https://agent402.tools/api/nft-metadata
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nft-metadata-resolver-4816076d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cgvBblFlFN8AfHIEIpHBe

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 nft-metadata-resolver-4816076d -d '<json body>'
```

Example prompt: Can you pull the metadata for token ID 4521 on contract 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D on Ethereum — I need its title, image, and traits?

## When to prefer this

Use this endpoint when you have a specific NFT contract address and token ID and need its display metadata (title, description, image, traits) without building your own indexing infrastructure. Ideal for single-token lookups on Ethereum, Base, Polygon, Arbitrum, or Optimism. Prefer this over general NFT indexers when you want a lightweight, pay-per-call approach without API key setup.

## Known failure modes

- Invalid or non-existent contract address returns an error
- Token ID not found on the specified contract
- Unsupported network name causes a validation error
- Malformed token ID (non-numeric, wrong format) causes a parse error
- Metadata URI is unreachable or returns invalid JSON (off-chain metadata failure)
- Payment not provided or insufficient USDC causes a 402 response

## How this service works

Resolve the metadata for a single NFT: title, description, image URLs (original + cached CDN), attributes/traits, and the standard (ERC-721 vs ERC-1155). Useful when you have a contract+tokenId and need the display data without re-fetching the whole collection.

## Output

Returns the NFT's title, description, original image URL, cached CDN image URL, attributes/traits array, and the token standard (ERC-721 or ERC-1155) for the specified contract and token ID on the requested network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "network": {
   "type": "string",
   "description": "ethereum / base / polygon / arbitrum / optimism (default base)."
  },
  "tokenId": {
   "type": "string",
   "description": "Token ID as a string (decimal or hex)."
  },
  "contract": {
   "type": "string",
   "description": "0x-prefixed 40-char NFT contract address."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "image": "https://example.com/azuki1.png",
  "title": "Azuki #1",
  "network": "ethereum",
  "tokenId": "1",
  "contract": "0xed5af388653567af2f388e6224dc7c4b3241c544",
  "standard": "ERC721",
  "attributes": [
   {
    "value": "Pink Hairband",
    "trait_type": "Hair"
   }
  ],
  "collection": "Azuki",
  "description": "Azuki starts with…"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nft-metadata-resolver-4816076d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)