# 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/uniswap.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-c453c591
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0vsVh1tQq-mduUyYmIbaj

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

Example prompt: Can you look up what Ethereum address uniswap.eth resolves to, along with any ENS records attached to it?

## When to prefer this

Use this endpoint when you need to resolve a human-readable .eth ENS name to its underlying Ethereum address or retrieve on-chain identity records. Prefer this over general blockchain APIs when you specifically need ENS resolution with associated records (text records, avatar, etc.) in a single call, especially in agentic workflows that accept .eth names as user inputs and need to convert them to addresses for transactions.

## Known failure modes

- ENS name not found or not registered — returns 404 or null address
- ENS name has no resolver set — returns error indicating unresolvable name
- Malformed ENS name input — returns 400 bad request
- ENS name expired or recently transferred — may return stale or empty records
- Network/RPC issues resolving on-chain data — returns 503 or timeout

## How this service works

Resolve ENS name to address and records

## Output

Returns the resolved Ethereum wallet address (0x...) for the given ENS name, along with any associated ENS records such as avatar, email, social handles, content hash, and other text records set by the domain owner.

## Example request

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

## More

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