# EVM Chain Read – ERC-20 Token Metadata

> EVM Chain Read – ERC-20 Token Metadata is a paid API for AI agents from chain-read.frcompanycheck.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-29).

Fetches ERC-20 token metadata (symbol, decimals, name) for a given token address on Base or Robinhood Chain via a pay-per-call x402 micro-payment API

## Facts

- Endpoint: GET https://chain-read.frcompanycheck.workers.dev/v1/%7Bchain%7D/erc20/meta/%7Btoken%7D?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-chain-read-erc-20-token-metadata-b13e5d94
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PqfVqdWGSSr_6iSuKqFNK

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 evm-chain-read-erc-20-token-metadata-b13e5d94
```

Example prompt: What are the symbol and decimals for the ERC-20 token at address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base (chain 8453)?

## When to prefer this

Use this endpoint when you need lightweight, on-demand ERC-20 token metadata (symbol, decimals, name) on Base or Robinhood Chain without managing your own RPC node or API key. Ideal for agents that need to occasionally resolve token metadata without committing to a full blockchain indexer subscription. The pay-per-call x402 model makes it cost-effective for low-volume lookups.

## Known failure modes

- Invalid or non-ERC-20 contract address returns an error or empty/null fields
- Unsupported chain ID (not 8453 or 4663) returns a 400 or 404 error
- Payment not included or invalid x402 USDC payment causes a 402 Payment Required response
- Network or RPC timeout results in a 503 or gateway error
- Malformed token address (wrong length, non-hex) returns a validation error

## How this service works

Pay-per-call EVM reads on Base (8453) and Robinhood Chain (4663): native balance, block tip, ERC-20 meta/balance/allowance, is-contract. Public RPCs, no API key. x402 USDC on Base.

## Output

A JSON object containing the ERC-20 token's symbol (e.g. 'USDC'), decimals (e.g. 6), and optionally the token name, read directly from the on-chain contract on the specified EVM network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "symbol": "USDC",
  "decimals": 6
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-chain-read-erc-20-token-metadata-b13e5d94/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain-read.frcompanycheck.workers.dev](https://www.zero.xyz/host/chain-read.frcompanycheck.workers.dev/llms.txt)