# AgentShelf ENS Resolve

> AgentShelf ENS Resolve is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-22).

Resolves Ethereum Name Service (ENS) names to addresses (forward lookup) or addresses to ENS names (reverse lookup) on Ethereum mainnet

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/ens-resolve?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-ens-resolve-5eae8848
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BklsRiCb7W3taiA5trNlj

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 agentshelf-ens-resolve-5eae8848 -d '<json body>'
```

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

## When to prefer this

Use this endpoint when you need a simple, pay-per-call ENS forward (.eth name to address) or reverse (address to .eth name) lookup on Ethereum mainnet without managing your own node, RPC provider, or CCIP-read infrastructure. Prefer it over running your own ENS resolver when you need a lightweight, on-demand lookup in an agentic workflow. Note it does not support CCIP-read or offchain gateway names — for those, use a full ENS-aware RPC provider instead.

## Known failure modes

- ENS name not registered or expired — returns resolved: false
- Address has no reverse record set — returns resolved: false
- Both name and address sent simultaneously — request rejected (send only one)
- CCIP-read / offchain gateway names not supported — will not resolve
- Malformed address or non-.eth name — may return error or resolved: false
- Payment not sent or incorrect amount — 402 Payment Required response
- Network issues reaching Ethereum mainnet node — transient error

## How this service works

Call when an agent needs an Ethereum mainnet ENS forward (.eth to address) or reverse lookup. Send name or address, not both. No CCIP-read and no offchain gateway. Unresolved is resolved false. Send JSON {"name":"vitalik.eth"}. Exact $0.004 USDC on Base. Try unpaid POST /v1/sandbox/ens-resolve first.

## Output

Returns a JSON object indicating whether resolution succeeded (resolved: true/false) and, if successful, the resolved Ethereum address (for forward lookups) or ENS name (for reverse lookups). Unresolved names return resolved: false.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "examples": [
    "vitalik.eth"
   ],
   "description": "ENS name ending in .eth. Example: vitalik.eth. Looked up on the Ethereum mainnet registry only, with no CCIP-read. Send name or address, not both."
  },
  "address": {
   "type": "string",
   "description": "Address to reverse-resolve on Ethereum mainnet. Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Uses {address}.addr.reverse. Send address or name, not both."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-ens-resolve-5eae8848/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)