# x402 ENS Resolver

> x402 ENS Resolver is a paid API for AI agents from agentx402pay.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Resolves an ENS name to an Ethereum address, or reverse-resolves an EVM address to its primary ENS name

## Facts

- Endpoint: GET https://agentx402pay.com/api/ens-resolve?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-ens-resolver-078f9b82
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZO_ABdN6e_PLCT-YEi6Wr

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 x402-ens-resolver-078f9b82
```

Example prompt: What Ethereum address does vitalik.eth resolve to? And can you also do the reverse — take this address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 and find its primary ENS name?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call ENS resolution without running your own node or maintaining an RPC connection. Ideal for agents that occasionally need to resolve ENS names or reverse-lookup addresses in the context of blockchain workflows, user identification, or transaction enrichment, without the overhead of a full Ethereum RPC setup.

## Known failure modes

- ENS name not registered or has no resolver set — returns null or error
- Address has no primary ENS name set — returns null
- Invalid ENS name format — returns validation error
- Invalid EVM address format — returns bad request error
- ENS registry temporarily unreachable — returns upstream timeout
- Neither 'name' nor 'address' query param provided — returns missing parameter error

## How this service works

Resolve an ENS name to an address, or reverse-resolve an address to its primary ENS name

## Output

Returns either the resolved Ethereum address for a given ENS name (forward lookup) or the primary ENS name associated with a given EVM address (reverse lookup). If no record is found, the response will indicate the name or address could not be resolved.

## 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 to resolve, e.g. \"vitalik.eth\""
      },
      "address": {
       "type": "string",
       "description": "EVM address to reverse-resolve to its primary ENS name"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

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