# Foundry ENS Resolver

> Foundry ENS Resolver is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-01).

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

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/ens-resolve?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-ens-resolver-232966c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_epE4Bd6e8FAL2wMY_lMEK

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 foundry-ens-resolver-232966c9 -d '<json body>'
```

Example prompt: What Ethereum address does vitalik.eth resolve to? And while you're at it, also tell me the resolver contract being used.

## When to prefer this

Choose this endpoint when you need to resolve ENS names to Ethereum addresses or perform reverse ENS lookups on 0x addresses, especially within an agent workflow that handles Web3 identity. It is pay-per-call ($0.001 USDC) via x402, making it suitable for on-demand resolution without a subscription. Prefer this over running your own ENS resolution logic if you don't have direct Ethereum RPC access or want a managed, low-latency lookup.

## Known failure modes

- ENS name not registered or has no resolver — returns null address or error
- Ethereum address has no primary ENS name set — returns empty or null name
- Malformed input (neither a valid ENS name nor a valid 0x address) — likely 400 error
- ENS name registered but pointing to zero address — may return 0x000...000
- Network timeout if ENS resolution RPC is slow — may return 5xx
- Payment not included or insufficient — 402 Payment Required

## How this service works

ENS resolver: name to Ethereum address, or address to primary ENS name. Input: 'vitalik.eth' or a 0x address.

## Output

Returns a JSON object containing the resolved ENS name, the corresponding Ethereum address, the network (e.g. 'ethereum'), and the resolver contract address. Works bidirectionally: input an ENS name to get the address, or input a 0x address to get the primary ENS name.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "An ENS name or 0x address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "network": "ethereum",
  "resolver": "0x231b0Ee14048e9dCcD1d247744d114a4EB5E8E63"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-ens-resolver-232966c9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)