# Aether NFT Metadata Lookup (Base)

> Aether NFT Metadata Lookup (Base) is a paid API for AI agents from aether-x402.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Fetches on-chain NFT metadata (name, image, tokenURI) for a given contract and token ID on the Base network, paid via x402 (USDC on Base).

## Facts

- Endpoint: POST https://aether-x402.vercel.app/v1/base/nft-metadata?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aether-nft-metadata-lookup-base-14cb40a6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E1sLKhamwBDhEZAh6wy3g

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 aether-nft-metadata-lookup-base-14cb40a6 -d '<json body>'
```

Example prompt: What's the name and image for NFT token ID 42 from the Base contract 0x1234567890abcdef1234567890abcdef12345678?

## When to prefer this

Choose this endpoint when you need to resolve NFT metadata (name, image, tokenURI) for a specific token on the Base L2 network and want a pay-per-call model with no subscription. It is particularly useful for AI agents that already operate in the x402 micropayment ecosystem using USDC on Base, and need lightweight, on-demand NFT lookups without standing up their own RPC infrastructure.

## Known failure modes

- Invalid contract address format (not a valid 0x-prefixed 40-char hex) returns a 400 error
- Token ID does not exist on the contract returns a not-found or null metadata response
- Contract is not an NFT contract (ERC-721/1155) may return empty or error response
- IPFS gateway timeouts can cause slow or failed metadata resolution
- Payment failure or insufficient USDC balance results in 402 Payment Required
- Rate limits or network congestion on Base may cause transient failures

## How this service works

Pay-per-call Base onchain data, token risk verdicts and x402 payability audits over x402 (USDC on Base).

## Output

A JSON object containing the NFT's metadata (name, image URI, and other on-chain attributes) plus the raw tokenURI (often an IPFS link), enabling downstream display or verification of the asset.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokenId": {
   "type": [
    "string",
    "integer"
   ],
   "pattern": "^[0-9]+$"
  },
  "contract": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "metadata": {
   "name": "...",
   "image": "ipfs://..."
  },
  "tokenURI": "ipfs://..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aether-nft-metadata-lookup-base-14cb40a6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aether-x402.vercel.app](https://www.zero.xyz/host/aether-x402.vercel.app/llms.txt)