# ENS Resolver API

> ENS Resolver API is a paid API for AI agents from ens-resolver.api.klymax402.com, paid per call via x402, $0.002000/call, status unknown (last checked 2026-09-14).

Resolves ENS names to Ethereum addresses or reverse-resolves Ethereum addresses to ENS names

## Facts

- Endpoint: GET https://ens-resolver.api.klymax402.com/api/resolve
- Price: $0.002000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ens-resolver-api-klymax402-com-ed38caa3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kzq2LWHGORfIzrh4Qk-T4

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-resolver-api-klymax402-com-ed38caa3
```

Example prompt: What Ethereum address does vitalik.eth resolve to? Also, can you reverse-resolve 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 to get its ENS name?

## When to prefer this

Use this endpoint when you need to resolve a human-readable ENS name (e.g. vitalik.eth) to its underlying Ethereum address, or when you have an Ethereum address and want to find its associated ENS identity. Ideal for enriching wallet data with human-readable names, verifying ENS ownership, or preparing transactions using ENS names.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null or error
- Ethereum address has no reverse ENS record set — returns null
- Invalid ENS name format — returns validation error
- Invalid Ethereum address format — returns error
- ENS name exists but has no address record — returns null
- Network or RPC timeout when querying Ethereum mainnet

## How this service works

Resolve ENS name to Ethereum address or reverse-resolve address to ENS name

## Output

Returns the resolved Ethereum address for a given ENS name, or the ENS name associated with a given Ethereum address, depending on which input was provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "ENS name to resolve (e.g. vitalik.eth)"
  },
  "address": {
   "type": "string",
   "description": "Ethereum address for reverse resolution (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ens-resolver-api-klymax402-com-ed38caa3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ens-resolver.api.klymax402.com](https://www.zero.xyz/host/ens-resolver.api.klymax402.com/llms.txt)