# Ambolt ENS Resolve

> Ambolt ENS Resolve is a paid API for AI agents from api.ambolt.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Resolves an ENS name to its Ethereum address (or reverse-looks up a name from an address) via on-chain data.

## Facts

- Endpoint: GET https://api.ambolt.dev/v1/ens-resolve?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ambolt-ens-resolve-c45a72e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fnoVzHWuoBj4oC1R6WYGi

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 ambolt-ens-resolve-c45a72e8
```

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

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call ENS resolution without running your own Ethereum node or managing a full Web3 library. Ideal for AI agents that need to enrich a wallet address with a human-readable name, verify a recipient before a transfer, or display ENS identity in a UI. Prefer it over general blockchain RPC providers when you want a simple HTTP GET with a structured JSON response and no SDK dependency.

## Known failure modes

- ENS name does not exist or is unregistered — resolved: false returned
- Malformed ENS name (uppercase or invalid TLD) rejected by pattern validation
- Malformed Ethereum address rejected by pattern validation
- ENS name exists but has no address record set — resolved: false
- Network/RPC timeout causing upstream resolution failure
- Payment failure (402) if x402 micropayment not provided

## How this service works

Pay-per-call data tools for developers and AI agents: company registers, documents, tenders, rates and on-chain facts as MCP tools, x402 endpoints and Apify Actors.

## Output

Returns a JSON object containing the resolved ENS name, the associated Ethereum address (0x format), the chain ID and network name (e.g. ethereum mainnet), the resolver contract address, a boolean indicating whether resolution succeeded, and the timestamp of the resolution read.

## 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": {
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "POST"
     ]
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "name": {
       "type": "string",
       "pattern": "^[a-z0-9-]+(\\.[a-z0-9-]+)+$",
       "maxLength": 255,
       "description": "Lower-case ENS name, e.g. vitalik.eth."
      },
      "address": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{40}$",
       "description": "Address for a reverse lookup (used if name is not set)."
      }
     },
     "additionalProperties": false
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "vitalik.eth",
  "readAt": "2026-10-02T21:35:42.201Z",
  "address": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
  "chainId": 1,
  "network": "ethereum",
  "resolved": true,
  "resolver": "0x231b0ee14048e9dccd1d247744d114a4eb5e8e63"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ambolt-ens-resolve-c45a72e8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ambolt.dev](https://www.zero.xyz/host/api.ambolt.dev/llms.txt)