ToolAssay

Resolve ENS names to addresses and look up reverse records (address → ENS name)

Resolve ENS names to addresses and look up reverse records (address → ENS name) via viem against Ethereum mainnet public RPCs. ENS data lives on Ethereum L1 regardless of where the wallet is active. Use this when an agent needs to eNS name ↔ address, bidirectional on Ethereum mainnet.

Answeringour last check, 2026-10-18
1 of 1checks answered this week
241 msmedian answer time
$0.003listed price per call
$0.003price it asked us

Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.

Endpoint

GET https://agentstoolshub.com/api/v1/crypto/ens-resolve

CategoryMarket data
Provider hostagentstoolshub.com
Networkseip155:8453
Payment schemesexact
Self-reported calls, 30 days3 from 2 payers (the provider's figure, not ours)

Our checks, last 30 days

DayResultHTTPAskedTime
2026-10-18 valid payment request 402$0.003 241 ms

Example input (from the provider)

{
  "method": "GET",
  "queryParams": {
    "op": "resolve",
    "value": "vitalik.eth"
  },
  "type": "http"
}

Promised output schema (from the provider)

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "input": {
      "additionalProperties": false,
      "properties": {
        "method": {
          "enum": [
            "GET"
          ],
          "type": "string"
        },
        "queryParams": {
          "properties": {
            "op": {
              "description": "Operation",
              "enum": [
                "resolve",
                "lookup"
              ],
              "type": "string"
            },
            "value": {
              "description": "ENS name or address",
              "type": "string"
            }
          },
          "required": [
            "value"
          ],
          "type": "object"
        },
        "type": {
          "const": "http",
          "type": "string"
        }
      },
      "required": [
        "type",
        "method"
      ],
      "type": "object"
    },
    "output": {
      "properties": {
        "example": {
          "type": "object"
        },
        "type": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "type": "object"
    }
  },
  "required": [
    "input"
  ],
  "type": "object"
}

This page as JSON