# AgentsToolsHub ENS Resolver

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

Resolves ENS names to Ethereum addresses and performs reverse lookups (address to ENS name) against Ethereum mainnet via viem and public RPCs

## Facts

- Endpoint: GET https://agentstoolshub.com/api/v1/crypto/ens-resolve?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentstoolshub-ens-resolver-91e8c2db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cuXk92DSz7Qcrk8uhOzS1

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 agentstoolshub-ens-resolver-91e8c2db
```

Example prompt: What Ethereum address does vitalik.eth resolve to? Use ENS resolve on Ethereum mainnet.

## When to prefer this

Use this endpoint when an agent needs to bidirectionally resolve between ENS names and Ethereum addresses on mainnet. Prefer this over building custom viem/ethers.js logic when you need a simple, paid-per-call REST interface without managing your own RPC keys. Especially useful when the agent is already handling x402 micropayments and needs a lightweight ENS lookup without spinning up blockchain infrastructure.

## Known failure modes

- ENS name not registered or has no resolver — returns null or empty result
- Address has no reverse ENS record set — returns null
- Invalid ENS name format or malformed 0x address — returns validation error
- Ethereum mainnet RPC temporarily unavailable — returns timeout or service error
- ENS record exists but points to zero address — returned as-is

## How this service works

Resolve ENS names to addresses and look up reverse records (address → ENS name) via viem against Ethereum mainnet public RPCs. ENS data lives on Ethereum L1 regardless of where the wallet is active. Use this when an agent needs to eNS name ↔ address, bidirectional on Ethereum mainnet.

## Output

Returns the resolved Ethereum address for a given ENS name (resolve operation), or the ENS name associated with a given Ethereum address (lookup/reverse operation), pulled live from Ethereum L1 via viem and public RPCs.

## 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",
     "required": [
      "value"
     ],
     "properties": {
      "op": {
       "enum": [
        "resolve",
        "lookup"
       ],
       "type": "string",
       "description": "Operation"
      },
      "value": {
       "type": "string",
       "description": "ENS name or address"
      }
     }
    }
   },
   "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/agentstoolshub-ens-resolver-91e8c2db/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentstoolshub.com](https://www.zero.xyz/host/agentstoolshub.com/llms.txt)