# EVM Address Label Lookup

> EVM Address Label Lookup is a paid API for AI agents from agent402.tools, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns a human-readable label for a known EVM address from a curated dataset of stablecoins, DEX routers, bridges, and exchange wallets

## Facts

- Endpoint: POST https://agent402.tools/api/address-label
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-address-label-lookup-9ad2bf78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UGMwmkPJG1tAReOnBaFp8

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-address-label-lookup-9ad2bf78 -d '<json body>'
```

Example prompt: What is this Ethereum address? Can you label 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 for me — is it a known contract, exchange wallet, or bridge?

## When to prefer this

Use this endpoint when you need a quick, reliable label for a well-known EVM address from a curated, committed dataset — especially for major stablecoins (USDC, USDT, DAI), WETH, WBTC, popular DEX routers, L1↔L2 bridges, or large exchange wallets. Prefer this over on-chain lookups or Etherscan scraping when you need a fast, paid-but-deterministic answer for commonly encountered addresses in DeFi workflows.

## Known failure modes

- Address not found in curated dataset — returns unknown/null label
- Malformed address (not 0x-prefixed or wrong length) — validation error
- Payment failure via x402 protocol — 402 response
- Network timeout — retry recommended

## How this service works

Label a known EVM address from a curated, committed dataset: major stablecoin + token contracts (USDC on every chain we settle on, USDT, DAI, WETH, WBTC), DEX routers (Uniswap, 1inch, 0x), canonical L1↔L2 bridges, large exchange hot/cold wallets, and burn/system addresses. Deterministic and offline - the provenance field states the dataset revision. Unknown addresses return {found:false}, not an error.

## Output

A structured label for the queried EVM address, identifying it as a known entity such as a stablecoin contract (e.g. USDC on a specific chain), DEX router (Uniswap, 1inch, 0x), canonical L1/L2 bridge contract, or exchange hot/cold wallet. Returns null or unknown for unrecognized addresses.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "0x-prefixed 40-char EVM address to label."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "labels": [
   {
    "note": "Circle USD Coin (native)",
    "label": "USDC",
    "network": "base",
    "category": "token"
   }
  ],
  "address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "provenance": {
   "source": "curated in-repo dataset",
   "entries": 34,
   "updated": "2026-07-13"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-address-label-lookup-9ad2bf78/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)