# MoneyTools NFT Metadata & Owner Lookup

> MoneyTools NFT Metadata & Owner Lookup is a paid API for AI agents from tools.moneytools.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-05).

Fetches ERC-721/1155 NFT metadata, owner address, tokenURI, and storage type (on-chain, IPFS, or mutable server) for any token on major EVM chains

## Facts

- Endpoint: GET https://tools.moneytools.dev/v1/nft?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-05
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/moneytools-nft-metadata-owner-lookup-86c2db3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JPqesAQeTeGzuxQYGoukB

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 moneytools-nft-metadata-owner-lookup-86c2db3e
```

Example prompt: Can you look up the metadata and current owner for Bored Ape Yacht Club token #1234 — the contract is 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D on Ethereum? I also want to know if the metadata is stored on-chain or IPFS.

## When to prefer this

Use this endpoint when you need rich, resolved NFT metadata including the image URL and traits — not just the raw tokenURI — across multiple EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche). It is especially valuable when you need to know whether an NFT's metadata is permanently stored (on-chain or IPFS) versus hosted on a mutable server, which is critical for provenance or investment research. Its x402 micropayment model ($0.002 USDC per call) makes it suitable for pay-per-use agent workflows without requiring a subscription.

## Known failure modes

- Invalid or non-existent contract address returns an error
- Token ID not minted or out of range returns a not-found error
- Unsupported chain name returns a validation error
- IPFS/Arweave gateway timeout causes metadata resolution failure
- Mutable tokenURI server is unreachable, returning partial data
- Free tier (10/day) exhausted without payment credentials returns HTTP 402
- Invalid x402 payment or insufficient API key credits returns payment failure

## How this service works

NFT metadata + owner: ERC-721/1155 token: standard, collection name, owner, tokenURI resolved (IPFS/Arweave/data URI) and the metadata JSON with image URL; says whether metadata is on-chain, IPFS or a mutable server. Free tier 10/day; then $0.002 via x402 (HTTP 402 + PAYMENT-REQUIRED) or X-API-Key credits. Not charged on failure. $0.002 USDC per call via x402 on Base. Run by MoneyTools.

## Output

Returns a JSON object containing: token standard (ERC-721 or ERC-1155), collection name, current owner address, raw tokenURI, fully resolved metadata JSON (image URL, name, description, attributes/traits), and a flag indicating whether metadata is stored on-chain, on IPFS/Arweave, or on a mutable centralized server. Also includes payment info (whether a charge was applied, network, amount in USD, and transaction hash).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "chain",
      "contract",
      "tokenId"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "examples": [
        "ethereum"
       ],
       "description": "chain: base, ethereum, arbitrum, optimism, polygon, bsc, avalanche"
      },
      "tokenId": {
       "type": "string",
       "examples": [
        "1"
       ],
       "description": "token id"
      },
      "contract": {
       "type": "string",
       "examples": [
        "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"
       ],
       "description": "NFT contract"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "payment": {
       "type": "object",
       "properties": {
        "charged": {
         "type": "boolean"
        },
        "network": {
         "type": "string"
        },
        "amountUsd": {
         "type": "string"
        },
        "transaction": {
         "type": [
          "string",
          "null"
         ]
        }
       }
      },
      "freeTier": {
       "type": "object"
      },
      "_moneytools": {
       "type": "object",
       "description": "optional plan / partner hints"
      }
     },
     "description": "Tool-specific JSON result (see llms.txt / openapi.json). Always includes payment info.",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/moneytools-nft-metadata-owner-lookup-86c2db3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tools.moneytools.dev](https://www.zero.xyz/host/tools.moneytools.dev/llms.txt)