# Vextorium NFT Info Lookup

> Vextorium NFT Info Lookup is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Looks up ERC-721 or ERC-1155 NFT details including collection name, owner, token URI, and full metadata (name, description, image, attributes) across major EVM chains.

## Facts

- Endpoint: POST https://api.vextorium.com/nft-info-pago?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-nft-info-lookup-88b3f556
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kMQXBDIYMB8235SmLlLZ-

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 vextorium-nft-info-lookup-88b3f556 -d '<json body>'
```

Example prompt: Look up the NFT at contract address 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13d with token ID 1234 on Ethereum — I want the collection name, owner, image, and all its attributes.

## When to prefer this

Choose this endpoint when you need comprehensive NFT metadata — including owner, collection info, and parsed on-chain/off-chain attributes — in a single call across Base, Ethereum, Arbitrum, Optimism, or Polygon. It handles both ERC-721 and ERC-1155 standards and resolves token URIs automatically, making it ideal over raw RPC calls when you want ready-to-use metadata without building your own resolver.

## Known failure modes

- Invalid or non-existent contract address returns null fields or an error
- Token ID not found or burned returns null owner/metadata
- Network not supported beyond the five listed EVM chains
- Token URI points to unreachable or private IPFS/HTTP resource, causing metadata to be null
- Rate limiting or payment failure (x402) causes request rejection

## How this service works

NFT lookup (ERC-721 / ERC-1155): collection name, owner, token URI and metadata (name, description, image, attributes).

## Output

Returns a JSON object containing: the EVM network, contract address, token ID, collection name, collection symbol, token standard (ERC-721 or ERC-1155), current owner address, metadata URI, and full parsed metadata object (name, description, image URL, and attributes array).

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [
      "contrato",
      "token_id"
     ],
     "properties": {
      "red": {
       "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism",
        "polygon"
       ],
       "type": "string",
       "description": "EVM network (default base)"
      },
      "contrato": {
       "type": "string",
       "description": "NFT contract address"
      },
      "token_id": {
       "type": "integer",
       "description": "Token id"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "red": {
       "type": [
        "string",
        "null"
       ]
      },
      "simbolo": {
       "type": [
        "string",
        "null"
       ]
      },
      "contrato": {
       "type": [
        "string",
        "null"
       ]
      },
      "estandar": {
       "type": [
        "string",
        "null"
       ]
      },
      "token_id": {
       "type": [
        "string",
        "null"
       ]
      },
      "coleccion": {
       "type": [
        "string",
        "null"
       ]
      },
      "metadatos": {
       "type": [
        "string",
        "number",
        "boolean",
        "object",
        "array",
        "null"
       ]
      },
      "propietario": {
       "type": [
        "string",
        "null"
       ]
      },
      "uri_metadatos": {
       "type": [
        "string",
        "null"
       ]
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "red": "ethereum",
  "simbolo": "BAYC",
  "contrato": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D",
  "estandar": "ERC-721",
  "token_id": "1",
  "coleccion": "BoredApeYachtClub",
  "metadatos": null,
  "propietario": "0x46EFbAedc92067E6d60E84ED6395099723252496",
  "uri_metadatos": "ipfs://QmeSjSinHpPnmXmspMjwiXyN6zS4E9zccariGR3jxcaWtq/1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-nft-info-lookup-88b3f556/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)