# 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/ens.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-c2f40b47
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kAuwzFMbJ0pucmUIbO3MM

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-c2f40b47
```

Example prompt: What Ethereum wallet address does vitalik.eth resolve to? Can you also pull any ENS records attached to it?

## When to prefer this

Use this endpoint when you need to translate a human-readable ENS name (e.g. alice.eth) into an Ethereum wallet address or retrieve ENS profile records for identity enrichment, wallet lookups, or pre-transaction address validation. Prefer this over a full blockchain node query when you need a fast, low-cost REST API call without setting up an Ethereum provider.

## Known failure modes

- ENS name does not exist or has never been registered — returns not found or null address
- ENS name is expired and no longer resolves — returns error or empty result
- ENS name has no resolver set — records unavailable
- Malformed ENS name input (missing .eth or invalid characters) — returns 400/validation error
- Rate limit exceeded — returns 429
- Payment not provided or insufficient — returns 402 payment required

## How this service works

Resolve ENS name to address and records

## Output

Returns the resolved Ethereum address (0x...) for the given ENS name, along with associated on-chain records such as text records (email, Twitter, avatar, website), content hash, and other metadata stored in the ENS resolver contract.

## Example request

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-web3identity-com-c2f40b47/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)