# ENS Name Resolver

> ENS Name Resolver is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Resolves an Ethereum Name Service (ENS) name (e.g. vitalik.eth) to its corresponding Ethereum address

## Facts

- Endpoint: POST https://twin.unykorn.org/ens-resolve?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-name-resolver-27279930
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yZO5QJcaOzl5ZjdC9JUXH

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 ens-name-resolver-27279930 -d '<json body>'
```

Example prompt: What Ethereum address does vitalik.eth resolve to?

## When to prefer this

Choose this endpoint when you need a simple, pay-per-call ENS resolution without managing your own Ethereum node or ENS library. It is ideal for lightweight agents that occasionally need to resolve .eth names to 0x addresses without infrastructure overhead, and when you want a verifiable receipt for each resolution call.

## Known failure modes

- ENS name not registered or has no resolver — returns an error or null address
- ENS name expired or no primary address set — lookup returns empty result
- Invalid ENS name format (e.g. missing .eth suffix or contains invalid characters) — validation error
- Network or RPC node unavailability causing resolution timeout
- Payment failure prevents the request from being processed

## How this service works

Resolve an ENS name to an Ethereum address — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, a type field set to 'ens-resolve', the resolved Ethereum address, and a receipt containing the transaction hash (tx_hash), amount paid in USD, and a unique receipt ID for auditing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "name": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "ens-resolve",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.005,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-name-resolver-27279930/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)