All guides

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

Resolve an ENS name to its Ethereum address, or look up the primary name of an address, read from the ENS registry on Ethereum mainnet. Pay per call.

Wallets, bots and agents see names like vitalik.eth and addresses in the same messages. One call resolves a name to its Ethereum address or finds the reverse-record name of an address, read through the ENS registry on Ethereum mainnet.

Only on-chain resolvers are supported. Names that need off-chain (CCIP-read) resolution report resolved=false instead of a guess.

The calls

Each call returns 402 with the price until a payment is attached; an x402 client pays and retries automatically. Calls that fail are not charged. See Get started and the guide for bots and agents for code.

ens-resolve $0.003 per call

Resolve an ENS name (e.g.

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

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

Questions

Which chain does it read?

Ethereum mainnet through the ENS registry.

What about off-chain names?

They report resolved=false; the call does not guess.

Can I look up an address?

Yes. Pass address to get its reverse-record name when one is set.

Use it from an AI agent

Every call is also an MCP tool: add https://api.ambolt.dev/mcp to your agent's server list.