# FiatDock ERC-20 Token Metadata

> FiatDock ERC-20 Token Metadata is a paid API for AI agents from fiatdock.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Returns name, symbol, decimals, and total supply for any ERC-20 token contract on Base

## Facts

- Endpoint: POST https://fiatdock.com/v1/chain/token-metadata
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fiatdock-erc-20-token-metadata-a50d1837
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_207I_xjHRH9xFJO3z3UX7

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 fiatdock-erc-20-token-metadata-a50d1837 -d '<json body>'
```

Example prompt: What's the name, symbol, decimals, and total supply of the ERC-20 token at contract address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base?

## When to prefer this

Use this endpoint when you need authoritative on-chain token metadata (name, symbol, decimals, total supply) for any ERC-20 on Base without maintaining your own RPC node. Prefer it over token price/safety endpoints when you only need structural metadata, not market data or risk signals. It is ideal for normalizing raw token amounts (using decimals), labeling tokens in a UI, or verifying a contract's identity before executing a transaction.

## Known failure modes

- Invalid or non-ERC-20 contract address returns an error — the address may be an EOA or non-token contract
- Contract not deployed on Base returns a not-found or zero-data response
- Malformed contract address (wrong length, bad checksum) returns a validation error
- Payment failure via x402 (insufficient USDC) results in a 402 Payment Required response
- Network congestion may cause slightly stale totalSupply if chain RPC is delayed

## How this service works

ERC-20 token metadata on Base — name, symbol, decimals, total supply. Pay-per-call via x402.

## Output

A JSON object containing the token's official name, ticker symbol, decimal precision, total supply as a formatted number, total supply in atomic units, the contract address, network identifier (base), and a timestamp of when the data was fetched.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "description": "An ERC-20 contract address (0x…) on Base"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "asOf": "2026-07-30T00:00:00.000Z",
  "name": "USD Coin",
  "symbol": "USDC",
  "network": "base",
  "contract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "decimals": 6,
  "totalSupply": "4200000000",
  "totalSupplyAtomic": "4200000000000000"
 }
}
```

## More

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