# ChainScope ENS Resolve

> ChainScope ENS Resolve is a paid API for AI agents from chainsscope.duckdns.org, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Resolves an ENS (Ethereum Name Service) domain name to its corresponding Ethereum wallet address

## Facts

- Endpoint: POST https://chainsscope.duckdns.org/tools/ens-resolve
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainscope-ens-resolve-651befcd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AQ0NqZLuIU-i1C73bUpd8

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 chainscope-ens-resolve-651befcd -d '<json body>'
```

Example prompt: Can you resolve vitalik.eth to its actual Ethereum wallet address for me?

## When to prefer this

Use this endpoint when you need to programmatically resolve a human-readable ENS domain (e.g. name.eth) to an Ethereum wallet address within a multi-chain intelligence workflow. Prefer this over building your own ENS resolution when you want a single consistent API interface that is part of a broader wallet and address intelligence suite. Ideal for AI agents that need to enrich transaction flows, verify identity, or route payments to ENS names without managing separate ENS library dependencies.

## Known failure modes

- ENS name does not exist or has no resolver set — returns null address
- ENS name is expired or transferred — returns stale or no address
- Invalid input format (not a valid .eth name) — may return error or null
- Network issues reaching ENS registry — service timeout
- Rate limiting or payment failure — request rejected

## How this service works

Turn a .eth name into an address, or an address into its primary .eth name -- one endpoint, auto-detects which direction based on the input. Ethereum mainnet only (ENS has no separate Base deployment).

## Output

Returns a JSON object containing the original ENS query string, the resolved Ethereum wallet address (as a 0x hex string), and the canonical resolved name. If the ENS name cannot be resolved, resolved_address may be null.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": ".eth name or 0x address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "query": "vitalik.eth",
  "resolved_name": null,
  "resolved_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
 }
}
```

## More

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