# Coin Railz Token Metadata Lookup

> Coin Railz Token Metadata Lookup is a paid API for AI agents from coinrailz.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Returns on-chain metadata (name, symbol, decimals, total supply) for any token contract address on a specified blockchain network

## Facts

- Endpoint: POST https://coinrailz.com/x402/service/token-metadata
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coin-railz-token-metadata-lookup-e3000571
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mz5tOCqxsN5cCR_WzvUWG

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 coin-railz-token-metadata-lookup-e3000571 -d '<json body>'
```

Example prompt: What are the name, symbol, decimals, and total supply for the token at contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum?

## When to prefer this

Use this endpoint when you need authoritative on-chain token metadata (name, symbol, decimals, total supply) for a specific contract address across any supported blockchain. Prefer this over price endpoints when you need structural token information for UI rendering, amount calculations, or DeFi agent setup rather than market data. Ideal when building trading UIs, normalizing token amounts, or validating a token contract identity.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty metadata
- Unsupported chain identifier causes a rejection or null response
- Token contract exists but is non-standard (e.g. missing name/symbol functions) may return partial data
- Network congestion or RPC issues may cause timeouts
- Incorrect chain specified for a valid address returns wrong or no data

## How this service works

Unified token info across all chains - essential building block for trading agent UIs (B2B2C infrastructure)

## Output

A JSON object containing the token's name (e.g. 'USD Coin'), symbol (e.g. 'USDC'), decimals (e.g. 6), and total supply as a string representing the raw on-chain value for the specified contract address and chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "chain",
  "tokenAddress"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Blockchain network"
  },
  "tokenAddress": {
   "type": "string",
   "description": "Token contract address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "Token name"
  },
  "symbol": {
   "type": "string",
   "description": "Token symbol"
  },
  "decimals": {
   "type": "number",
   "description": "Token decimals"
  },
  "totalSupply": {
   "type": "string",
   "description": "Total supply"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coin-railz-token-metadata-lookup-e3000571/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from coinrailz.com](https://www.zero.xyz/host/coinrailz.com/llms.txt)
