# ERC-20 Token On-Chain Metadata Reader

> ERC-20 Token On-Chain Metadata Reader is a paid API for AI agents from task-radar-x402.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-31).

Reads ERC-20 token metadata (name, symbol, decimals, total supply) directly from on-chain public RPC nodes across multiple EVM chains.

## Facts

- Endpoint: GET https://task-radar-x402.vercel.app/api/erc20?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/erc-20-token-on-chain-metadata-reader-189b27de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pCWYbp17nmlpeW79_ahwD

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 erc-20-token-on-chain-metadata-reader-189b27de
```

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

## When to prefer this

Use this endpoint when you need authoritative, on-chain ERC-20 metadata directly from the blockchain rather than a centralized data provider. Prefer this over CoinGecko or CoinMarketCap when you have a contract address but no ticker, when you need decimals for precise token math, when verifying total supply against claimed figures, or when the token is too new or obscure to appear in off-chain databases. Supports Ethereum, Base, Arbitrum, Optimism, Polygon, and BSC.

## Known failure modes

- Invalid or non-ERC-20 contract address returns an error or empty fields
- Unsupported chain name returns a validation error
- Contract not deployed on specified chain returns null or RPC error
- RPC node temporarily unavailable causes timeout or 5xx error
- Address is a non-standard token that doesn't implement standard ERC-20 interface methods

## How this service works

ERC-20 token metadata read on-chain: name, symbol, decimals, total supply (public RPC). 0.01 USDC/call on Base.

## Output

Returns the ERC-20 token's on-chain metadata including: human-readable name (e.g. 'USD Coin'), ticker symbol (e.g. 'USDC'), decimals (e.g. 6), and total supply (as a raw integer from the contract). Data is fetched live from the chain's public RPC node.

## 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",
     "properties": {
      "chain": {
       "type": "string",
       "description": "ethereum|base|arbitrum|optimism|polygon|bsc (default ethereum)"
      },
      "address": {
       "type": "string",
       "description": "Token address"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/erc-20-token-on-chain-metadata-reader-189b27de/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from task-radar-x402.vercel.app](https://www.zero.xyz/host/task-radar-x402.vercel.app/llms.txt)