# ERC-20 Token Contract Name Lookup

> ERC-20 Token Contract Name Lookup is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Returns the name string of an ERC-20 token contract on a specified EVM-compatible blockchain

## Facts

- Endpoint: POST https://twin.unykorn.org/erc20-name?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/erc-20-token-contract-name-lookup-74789279
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ocUKX3LGXl87jmoQGN_5O

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-contract-name-lookup-74789279 -d '<json body>'
```

Example prompt: What's the name of the ERC-20 token contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum?

## When to prefer this

Use this endpoint when you need to resolve a human-readable name for an ERC-20 token given only its contract address and chain, especially across multiple EVM chains including Base, Arbitrum, Optimism, Polygon, and others. Prefer this over on-chain RPC calls when you don't have direct node access or want a simple pay-per-call REST interface without managing Web3 infrastructure.

## Known failure modes

- Contract address not found or not an ERC-20 contract — returns error or empty name
- Unsupported chain enum value — validation error
- Invalid contract address format (not 0x + 40 hex chars) — schema validation failure
- Network node unavailable or timeout for the specified chain
- Contract exists but has no name function (non-standard ERC-20) — may return empty or error

## How this service works

Name of a token contract — Genesis402 / UnyKorn Operator Network

## Output

A JSON object containing a boolean ok field, the endpoint type ('erc20-name'), the resolved token contract name string, a timestamp, and a payment receipt with transaction hash, USD amount, and receipt ID.

## 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": "erc20-name",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.25,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/erc-20-token-contract-name-lookup-74789279/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)