# EVM Address Label / Known Address Lookup

> EVM Address Label / Known Address Lookup is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Looks up human-readable labels for known EVM blockchain addresses (e.g. exchange names, protocol contracts, wallet tags)

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/mini/evm.address-label--known-address-lookup
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-address-label-known-address-lookup-993935c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_L1BZSOrk7NgQi9up-ditg

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-known-address-lookup-993935c1 -d '<json body>'
```

Example prompt: Can you look up the label for the Ethereum address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 and tell me if it's a known entity like an exchange or protocol?

## When to prefer this

Use this endpoint when you need to resolve or annotate raw EVM/Ethereum addresses with human-readable names from a curated known-address database. Prefer this over on-chain ENS resolution when you want off-chain entity labels (exchanges, protocols, DAOs) rather than user-registered names. Best for blockchain analytics, transaction enrichment, and compliance workflows where identifying the real-world entity behind an address is critical.

## Known failure modes

- Unknown address returns no label or empty result
- Invalid EVM address format causes input validation error
- Address exists but has no known label in the database
- Service unavailable or payment not processed returns 402 or 5xx
- Input object missing required fields returns schema validation error

## How this service works

Machine-readable settlement service

## Output

Returns a structured object containing the human-readable label or name associated with the given EVM address, potentially including entity type (e.g. exchange, protocol, DAO), and confidence or source metadata if available. Returns an empty or null label if the address is not in the known-address database.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-address-label-known-address-lookup-993935c1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pennyrail.vercel.app](https://www.zero.xyz/host/pennyrail.vercel.app/llms.txt)