# ENS Name & Address Resolver

> ENS Name & Address Resolver is a paid API for AI agents from api.agent-data.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-14).

Resolves ENS names to Ethereum addresses (and vice versa), returning avatar, URL, Twitter/X, GitHub, and other on-chain profile records.

## Facts

- Endpoint: GET https://api.agent-data.workers.dev/api/v1/ens?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-name-address-resolver-9f2fa411
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bxL1uaG7912CXZ0y_ORz8

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-9f2fa411
```

Example prompt: What Ethereum address does vitalik.eth resolve to, and can you also pull back any Twitter or GitHub profiles linked to that ENS name?

## When to prefer this

Use this endpoint when you need to resolve ENS names to Ethereum addresses or reverse-lookup addresses to their primary ENS names within an agentic workflow that already uses x402 micropayments. It is ideal when you also want social profile metadata (Twitter, GitHub, avatar) alongside the address in a single call, without self-hosting an ENS resolver or running your own Ethereum node.

## Known failure modes

- ENS name does not exist or has no resolver — returns empty or error response
- Address has no primary ENS name set — name field absent or null
- Profile records exist on-chain but specific fields (avatar, Twitter) not set — partial records object returned
- Malformed ENS name or invalid 0x address in query — validation error
- Cloudflare Worker timeout or upstream ENS node outage — 5xx error

## How this service works

ENS resolution: name.eth -> address, or address -> verified primary name, plus avatar, url, X/Twitter, GitHub and other profile records.

## Output

A JSON object containing the resolved ENS name, the corresponding 0x Ethereum address, a verified boolean flag, and a records object with optional fields including url (website), com.twitter (Twitter/X handle), com.github (GitHub username), and avatar URI.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "name": {
       "type": "string",
       "description": "ENS name, e.g. vitalik.eth"
      },
      "address": {
       "type": "string",
       "description": "0x address (instead of name)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "records": {
   "url": "https://vitalik.ca",
   "com.twitter": "VitalikButerin"
  },
  "verified": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-name-address-resolver-9f2fa411/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agent-data.workers.dev](https://www.zero.xyz/host/api.agent-data.workers.dev/llms.txt)
