# EVM Token Metadata Lookup

> EVM Token Metadata Lookup is a paid API for AI agents from free-asset-radar-x402.besenok2018.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-30).

Returns on-chain metadata for an EVM token contract address, including symbol, decimals, network, and total supply.

## Facts

- Endpoint: GET https://free-asset-radar-x402.besenok2018.workers.dev/api/x402/evm-token-metadata?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-token-metadata-lookup-29906623
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QLGcMNgWWUQQGTeaYG2Xm

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-token-metadata-lookup-29906623
```

Example prompt: Can you look up the token metadata for the contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on the Base network and tell me its symbol, decimals, and total supply?

## When to prefer this

Choose this endpoint when an agent needs lightweight, fast EVM token metadata (symbol, decimals, total supply) for a known contract address without requiring a full blockchain node connection. Ideal for DeFi workflows, wallet UIs, or pre-trade checks where token precision and identity must be confirmed programmatically.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty metadata
- Unsupported network causes a lookup failure
- Rate limiting or payment failure returns a 402 response
- Malformed address format returns a validation error
- Token contract exists but does not implement standard ERC-20 metadata methods

## How this service works

Stable edge-hosted x402 utilities for autonomous agents.

## Output

A JSON object containing the token contract address, symbol (e.g. 'USDC'), network name (e.g. 'base'), number of decimals (e.g. 6), and total supply as a string.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "token": "0x...",
  "symbol": "USDC",
  "network": "base",
  "decimals": 6,
  "totalSupply": "1000000"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-token-metadata-lookup-29906623/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from free-asset-radar-x402.besenok2018.workers.dev](https://www.zero.xyz/host/free-asset-radar-x402.besenok2018.workers.dev/llms.txt)
