# ENS Name Resolver

> ENS Name Resolver is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0216/call, status unknown (last checked 2026-09-16).

Resolves an ENS name (e.g. vitalik.eth) to its Ethereum address, avatar URL, and resolver contract

## Facts

- Endpoint: GET https://api.strale.io/x402/ens-resolve
- Price: $0.0216/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-strale-io-1c1808c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O1JLZTYdIa3C4GRgPlA6D

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-strale-io-1c1808c6
```

Example prompt: What Ethereum wallet address does 'vitalik.eth' resolve to on ENS? Also grab the avatar URL and resolver contract if available.

## When to prefer this

Use this endpoint when you need to programmatically convert a human-readable ENS name (including .eth names, DNS names on ENS, and subdomains) to an Ethereum address, especially when you also need the associated avatar URL or resolver contract in a single call. Prefer this over on-chain calls when you want a simple REST API without managing an Ethereum node or web3 library.

## Known failure modes

- ENS name not found or unregistered — resolved: false returned
- Invalid ENS name format — input validation error
- ENS name has no address record set — empty address field
- Payment not provided or insufficient — 402 Payment Required response
- Network or ENS infrastructure timeout — 5xx error

## How this service works

Resolve an ENS name to its Ethereum address. Supports all ENS names including .eth, DNS names on ENS, and subdomains. Also returns avatar URL and resolver contract.

## Output

Returns the resolved Ethereum address, a boolean indicating whether resolution succeeded, the ENS name itself, and optionally an avatar URL associated with the name and the resolver contract address.

## Example request

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

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "description": "ENS name to resolve (e.g., 'vitalik.eth')"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

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