ENS Resolver

Resolve an ENS name, including .eth names, DNS names on ENS and subdomains, to its Ethereum address, avatar and resolver.

Pay by wallet (x402) ens-resolve

Example

Example answer
{
  "name": "thisdoesnotexist99999.eth",
  "address": null,
  "resolved": false,
  "resolver": null,
  "avatar_url": null
}

Inputs

FieldTypeRequiredWhat it is
namestringYesENS name to resolve (e.g., 'vitalik.eth')

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
namestringUsually (present for most inputs)
addressstringUsually (present for most inputs)
resolvedbooleanUsually (present for most inputs)
avatar_urlstringUsually (present for most inputs)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "ens-resolve",
    "inputs": {
      "name": "vitalik.eth"
    },
    "max_price_cents": 2
  }'

Limitations

  • Output reflects Public Ethereum RPC (publicnode.com, llamarpc.com) at query time. Dependent on upstream API availability; may degrade if the provider rate-limits or is temporarily unavailable.