# ERC-20 Token Metadata Lookup

> ERC-20 Token Metadata Lookup is a paid API for AI agents from x402helper.xyz, paid per call via x402, $0.006/call, status unknown (last checked 2026-10-31).

Fetches metadata for an ERC-20 token contract address across multiple EVM networks

## Facts

- Endpoint: GET https://x402helper.xyz/89e509/token/meta?utm_source=zero.xyz
- Price: $0.006/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-metadata-lookup-97793ebe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DGvrYWxZQrPqxS9nsDrqD

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-metadata-lookup-97793ebe
```

Example prompt: Can you look up the metadata for the ERC-20 token at contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — I need the name, symbol, and decimals.

## When to prefer this

Use this endpoint when you need on-chain ERC-20 token metadata (name, symbol, decimals) for a specific contract address on EVM-compatible networks including Base, Ethereum, Arbitrum, Optimism, Polygon, or BNB Chain. It is best suited for lightweight, per-token lookups rather than bulk indexing.

## Known failure modes

- Invalid or non-ERC-20 contract address returns an error or empty result
- Unsupported network name causes a validation error
- Contract address not found on the specified network returns failure
- Malformed 0x address format rejected by schema validation
- Network RPC unavailability may cause timeouts

## How this service works

X402 micropayments server — AI agents pay USDC for OFAC screening, rates, and billing verification.

## Output

Returns a JSON object with token metadata fields such as token name, symbol, decimals, and other ERC-20 contract-level information for the specified contract address on the requested EVM network.

## 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": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "token"
     ],
     "properties": {
      "token": {
       "type": "string",
       "default": null,
       "description": "ERC-20 contract address (0x..)"
      },
      "network": {
       "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism",
        "polygon",
        "bnb"
       ],
       "type": "string",
       "default": null,
       "description": "EVM network to read from (default base)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "success": true
 }
}
```

## More

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