# ENS Name/Address Resolver

> ENS Name/Address 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-29).

Resolves an ENS name to its Ethereum address, or reverse-resolves an Ethereum address to its primary ENS name, in a single API call.

## Facts

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

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-address-resolver-9040249b -d '<json body>'
```

Example prompt: Can you resolve vitalik.eth to its Ethereum wallet address using ENS?

## When to prefer this

Choose this endpoint when you need a quick, single-call ENS forward or reverse resolution without setting up your own Ethereum RPC node or ENS SDK. It is ideal for AI agents that need to translate human-readable ENS names to wallet addresses (or vice versa) on demand, especially in pay-per-call agentic workflows using the x402 protocol. Prefer this over raw RPC calls when you want a managed, metered API without infrastructure overhead.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null or error
- Ethereum address has no primary ENS name registered — returns empty or null name
- Invalid ENS name format — returns validation error
- Invalid Ethereum address format (not 0x + 40 hex chars) — schema validation failure
- ENS resolution RPC timeout or node unavailability — returns service error
- Payment failure via x402 — 402 Payment Required response before resolution is attempted

## How this service works

ENS in one call: resolve a name to an address, or an address to its primary name — Genesis402 / UnyKorn Operator Network

## Output

Returns either the resolved Ethereum address (0x-prefixed) for a given ENS name, or the primary ENS name (e.g. example.eth) for a given Ethereum address. If no resolution exists, the response will indicate the name or address could not be resolved.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "name": {
     "type": "string",
     "description": "string"
    },
    "address": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$",
     "description": "0x-prefixed 40-hex EVM address"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-name-address-resolver-9040249b/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)