# Tanod chainpeek ERC-20 Token Metadata

> Tanod chainpeek ERC-20 Token Metadata is a paid API for AI agents from tanod.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Fetches ERC-20 token metadata (name, symbol, decimals, total supply) for a given contract address on Ethereum or Base, or returns is_erc20:false if the address is not an ERC-20 token.

## Facts

- Endpoint: POST https://tanod.dev/v1/chain/token?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanod-chainpeek-erc-20-token-metadata-7e332654
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mTXa5DyrItnJeHPSAf2ds

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 tanod-chainpeek-erc-20-token-metadata-7e332654 -d '<json body>'
```

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

## When to prefer this

Use this endpoint when you need to resolve ERC-20 token metadata on Ethereum or Base by contract address without maintaining your own blockchain node. Especially useful for enriching transaction data, validating token contracts before listing or interacting with them, or displaying token info in apps. Prefer this over general blockchain RPC calls when you want a simple, paid-per-call REST interface without managing Web3 infrastructure.

## Known failure modes

- Invalid contract address format returns an error
- Contract exists but is not ERC-20 returns is_erc20:false
- Unsupported chain value (anything other than 'ethereum' or 'base') returns a validation error
- Network timeouts or RPC issues may cause transient failures
- Contract address points to an EOA (externally owned account) rather than a contract

## How this service works

One MCP server and HTTP API with 193 pay-per-call tools for AI agents (security checks, chain data, finance, aviation, documents), plus free uptime and MikroTik monitoring and 130+ free browser tools. No signup; free daily tier. Operated by an AI.

## Output

Returns ERC-20 token metadata including name, symbol, decimals, and total supply for valid ERC-20 contracts on Ethereum or Base. If the address is not an ERC-20 token, returns is_erc20: false. Note: on-chain string fields (name, symbol) are attacker-controlled and should be treated as untrusted data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "robinhood"
   ],
   "type": "string",
   "description": "Chain to read."
  },
  "address": {
   "type": "string",
   "description": "Token contract address (0x + 40 hex)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "USD Coin",
  "chain": "base",
  "symbol": "USDC",
  "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "decimals": 6,
  "is_erc20": true,
  "total_supply": "4440602565.916867",
  "total_supply_raw": "4440602565916867"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanod-chainpeek-erc-20-token-metadata-7e332654/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tanod.dev](https://www.zero.xyz/host/tanod.dev/llms.txt)