# ENS Resolve

> ENS Resolve is a paid API for AI agents from apexfaucet.xyz, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-15).

Resolves an ENS .eth name to its Ethereum address, or reverse-resolves an Ethereum address to its primary ENS name with forward-verification.

## Facts

- Endpoint: GET https://apexfaucet.xyz/api/x402/ens-resolve?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-resolve-a9e981e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e-IyJi4gTlj7JAQ_USdGS

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-resolve-a9e981e0
```

Example prompt: What Ethereum address does vitalik.eth resolve to? And while you're at it, what's the forward-verified ENS name for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?

## When to prefer this

Use this endpoint when you need to resolve ENS names to Ethereum addresses or reverse-resolve addresses to their primary ENS names with forward-verification guarantee. It is particularly valuable when you need verified, trustworthy ENS resolution (no spoofed reverse records) at a low per-call cost of $0.002 USDC. Prefer this over raw RPC calls when you need a simple HTTP API without managing your own Ethereum node or ENS library setup.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null or error
- Address has no primary ENS name set — returns empty/null name
- Reverse record exists but fails forward verification (points elsewhere) — not returned as a valid name
- Invalid address format (not a valid 0x... hex address) — input validation error
- Neither name nor address parameter provided — returns error about missing required parameter
- Both name and address provided simultaneously — ambiguous input error
- Network/RPC issues preventing ENS resolution — upstream timeout or error

## How this service works

ENS resolve on Ethereum: a .eth name to its address (?name=vitalik.eth), or an address to its primary ENS name (?address=0x...), forward-verified so a reverse record pointing elsewhere is never returned as the name.

## Output

Returns either the resolved Ethereum address (0x...) for a given ENS name, or the forward-verified primary ENS name for a given Ethereum address. Forward verification ensures the reverse record actually points back to the queried address, preventing spoofed or mismatched ENS names from being returned.

## 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": "An ENS name to resolve to an address. Pass name OR address."
      },
      "address": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "description": "An address to look up its ENS name (forward-verified). Pass name OR address."
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-resolve-a9e981e0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexfaucet.xyz](https://www.zero.xyz/host/apexfaucet.xyz/llms.txt)