# ENS Name Resolver

> ENS Name Resolver is a paid API for AI agents from api.web3identity.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves an ENS (Ethereum Name Service) name to its underlying Ethereum address and associated records

## Facts

- Endpoint: GET https://api.web3identity.com/api/ens/resolve/vitalik.eth
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-web3identity-com-bc48a196
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lLt-DIN_S9Z3VveRbA6GP

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 api-web3identity-com-bc48a196
```

Example prompt: What Ethereum wallet address and records are registered to vitalik.eth? Look it up and give me the full resolution details.

## When to prefer this

Use this endpoint when you need to resolve an ENS human-readable name (e.g. vitalik.eth) to its Ethereum address or associated records. Prefer this over manual on-chain lookups or general blockchain RPCs when you want a simple REST API call with aggregated ENS record data including avatar and text records in one response.

## Known failure modes

- ENS name not found or not registered — returns 404 or null address
- ENS name has expired and is no longer resolving — returns empty or error response
- Invalid ENS name format — returns 400 bad request
- Upstream ENS resolution network unavailable — returns 503
- ENS name resolves to zero address (0x000...000) indicating unset resolver

## How this service works

Resolve ENS name to address and records

## Output

Returns the resolved Ethereum address for the given ENS name along with associated ENS records such as text records, avatar, content hash, and other on-chain metadata stored under the name.

## Example request

```json
{
 "name": "vitalik.eth"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-web3identity-com-bc48a196/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.web3identity.com](https://www.zero.xyz/host/api.web3identity.com/llms.txt)