ENS Resolve: ENS Name to Address and Address to Primary Name

Resolve an ENS name (e.g. vitalik.eth) to its Ethereum address, or look up the reverse-record name of an address, via the ENS registry on Ethereum mainnet. Onchain resolvers only; off-chain (CCIP-read) names report resolved=false.

x402: $0.003 per callMCP tool: ens_resolve

Input

Parameter	Type	Default	Description
`name`	string		Lower-case ENS name, e.g. vitalik.eth.
`address`	string		Address for a reverse lookup (used if name is not set).

* required

Source and freshness

Source and licence: Stated in every response (field source).
Last verified: 2026-10-03 (hourly check against the live source)

Use it

HTTP (x402)

curl -i "https://api.ambolt.dev/v1/ens-resolve?name=vitalik.eth"

Returns 402 Payment Required with the price until an x402 payment is attached; @x402/fetch does this for you. See Get started.

MCP

{ "mcpServers": { "ambolt": { "url": "https://api.ambolt.dev/mcp" } } }
# then call the tool: ens_resolve

Apify

Not published as an Actor yet.

Example response

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

Good to know

You are charged only when the call succeeds. Invalid input or an unavailable source costs nothing.
Every response states its source and the time it was fetched.
Informational only; not financial, legal or tax advice.
Something wrong or missing? Open an issue on the repository (ambolt-mcp) and a reply follows under the Ambolt name.

Guides

ENS resolver API: ENS name to address and address to name