# EVM Token Info (Name, Symbol, Decimals, Supply)

> EVM Token Info (Name, Symbol, Decimals, Supply) is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Returns the name, symbol, decimals, and total supply of an ERC-20 token contract on a supported EVM chain in a single call.

## Facts

- Endpoint: POST https://twin.unykorn.org/evm-token-info?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-token-info-name-symbol-decimals-supply-625682a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rbFrg1X-osNW2WD1xWnV2

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-info-name-symbol-decimals-supply-625682a4 -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you need all four basic ERC-20 token metadata fields (name, symbol, decimals, total supply) in a single low-latency call across any of the ten supported EVM chains. It is ideal over raw RPC calls when you want a pay-per-use model without maintaining your own node infrastructure, and over multi-call alternatives when you want a single unified response with a payment receipt.

## Known failure modes

- Invalid contract address format (must be 0x followed by 40 hex chars) returns an error
- Unsupported chain name returns a validation error
- Contract address is not an ERC-20 token (e.g. EOA or non-standard contract) may return null or error fields
- Payment failure or insufficient USDC balance returns a 402 error
- Network timeout or RPC node unavailability returns a 5xx error

## How this service works

Name, symbol, decimals and supply of a token in one call — Genesis402 / UnyKorn Operator Network

## Output

A JSON object with ok:true, the type field 'evm-token-info', token metadata fields (name, symbol, decimals, total supply), a receipt containing the transaction hash, USD amount charged, and a receipt ID, plus a generated_at ISO8601 timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "chain": {
     "enum": [
      "ethereum",
      "base",
      "polygon",
      "arbitrum",
      "optimism",
      "bsc",
      "avalanche",
      "gnosis",
      "linea",
      "scroll"
     ],
     "type": "string"
    },
    "contract": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "evm-token-info",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.005,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-token-info-name-symbol-decimals-supply-625682a4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)
