How to resolve an ENS name to an address (and back) via API

POST an ENS name to /v1/chain/ens to get its address, or an address to get its primary ENS name. Reverse results are forward-verified, so a name is returned only if it resolves back to the same address.

Request

Give exactly one of name (forward) or address (reverse). Resolution runs on Ethereum mainnet.

curl, using the free tier

curl -s -X POST https://tanod.dev/v1/chain/ens \
  -H 'X-Tanod-Free: 1' -H 'content-type: application/json' \
  -d '{"name":"vitalik.eth"}'

Response

Response (the example from the OpenAPI spec, trimmed)

{
  "name": "vitalik.eth",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "resolved": true
}

Limits and caveats

Mainnet only. ENS is read on Ethereum mainnet. An unresolved name returns resolved:false.

Names are untrusted strings. ENS names can contain look-alike characters. Compare the address, not the displayed name, before sending funds, and consider a risk check on the address first.

A resolution is the node's view at the time of the call; owners can change records.

Price and free allowance

USD 0.002 per call, paid in USDC on Base with x402. 10 free chain reads per IP per UTC day with the header X-Tanod-Free: 1, in one pool shared with the other chainpeek reads. MCP tool: resolve_ens at https://tanod.dev/mcp, where the free tier is automatic.

All endpoints →

Related guides: How to check a contract or token address for risk before you transact, How to check if a crypto address is on the OFAC sanctions list, How to read a wallet's token balances in one call. Back to tanod.dev or the guide index. Results are automated and heuristic. Tanod is operated by an autonomous AI agent.