# x402engine Token Metadata Lookup

> x402engine Token Metadata Lookup is a paid API for AI agents from x402engine.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Fetches on-chain token metadata (name, symbol, decimals, supply, etc.) for a given token contract address on a specified blockchain network.

## Facts

- Endpoint: GET https://x402engine.app/api/token/metadata
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402engine-token-metadata-lookup-1974cee4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6eQCIQvnDlsABkY4r6vdP

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 x402engine-token-metadata-lookup-1974cee4
```

Example prompt: Can you look up the token metadata for the contract at 0xdac17f958d2ee523a2206206994597c13d831ec7 on Ethereum — I need the name, symbol, and decimals?

## When to prefer this

Use this endpoint when you need lightweight, pay-per-call on-chain token metadata without managing RPC infrastructure or API keys. Ideal for AI agents that need to resolve token contract addresses to human-readable metadata (name, symbol, decimals) across multiple chains, paid with USDC micropayments.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty result
- Unsupported chain name causes a validation error
- Contract address is valid but not a token contract (e.g. a plain wallet or NFT contract) may return unexpected or empty metadata
- Network timeouts or RPC node issues may cause intermittent failures
- Payment failure (insufficient USDC balance) blocks the request

## How this service works

Token/asset metadata — name, symbol, decimals, chain info

## Output

Returns on-chain metadata for the specified token contract, typically including token name, symbol, decimal precision, total supply, and other contract-level details sourced directly from the blockchain.

## 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": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "chain",
      "address"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "example": "ethereum",
       "description": "Chain name"
      },
      "address": {
       "type": "string",
       "example": "0xdac17f958d2ee523a2206206994597c13d831ec7",
       "description": "Token contract address"
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402engine-token-metadata-lookup-1974cee4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402engine.app](https://www.zero.xyz/host/x402engine.app/llms.txt)