# ENS Resolve

> ENS Resolve is a paid API for AI agents from ari001.tailb4ac3a.ts.net, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-10).

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

## Facts

- Endpoint: GET https://ari001.tailb4ac3a.ts.net/v1/ventures/x402_chain_reads_v1/ens_resolve?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-resolve-f980bfc3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LoZS7YClFHFbgXXsKibOh

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-f980bfc3
```

Example prompt: What Ethereum address does vitalik.eth resolve to? And can you also do the reverse — what ENS name is registered as the primary for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?

## When to prefer this

Use this endpoint when you need to resolve ENS names to Ethereum addresses or reverse-resolve addresses to ENS names on Ethereum mainnet, with the added safety of verified forward-confirmation on reverse lookups. Prefer this over a raw RPC call when you want a simple REST API with built-in verification logic rather than constructing raw JSON-RPC calls yourself.

## Known failure modes

- ENS name not registered or has no resolver — returns null or error
- Address has no primary ENS name set — returns empty or null
- Reverse resolution found a name but forward resolution doesn't match — verification fails
- Invalid input format (name not ending in .eth, address not matching 0x+40hex pattern) — schema validation error
- Network or RPC connectivity issues — server error response

## How this service works

ENS resolution on Ethereum mainnet. Pass name (an ASCII .eth name) to get its resolved address, or address (0x + 40 hex) to get its primary ENS name, reverse-resolved and verified forward.

## Output

For a forward lookup (name → address): returns the Ethereum address the .eth name resolves to. For a reverse lookup (address → name): returns the primary ENS name registered for that address, verified by also checking the forward resolution matches.

## 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",
     "properties": {
      "name": {
       "type": "string",
       "description": "an ASCII .eth name (forward), OR"
      },
      "address": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "description": "0x + 40 hex (reverse, verified)"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

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