# Reverse ENS Lookup: Wallet Address to ENS Name

**Use case:** 

Turn Ethereum wallet addresses into their primary ENS names and public profile: name, avatar, description, website, email, Twitter, GitHub and other handles set in ENS records, with a profile completeness score. For CRM and lead enrichment, analytics dashboards and on-chain research. Paste your own list of 0x addresses.

## Input

```json
{
  "mode": "resolve",
  "queries": [
    "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5"
  ],
  "textRecords": [
    "*standard",
    "*services"
  ],
  "coinTypes": [],
  "includeRegistration": true,
  "includeContenthash": false,
  "verifyReverse": true,
  "includeEvents": false,
  "eventsLimit": 20,
  "expiresWithinDays": 30,
  "lookupOwnedBy": true,
  "lookupResolvedTo": true,
  "onlyActive": true,
  "maxNamesPerQuery": 50,
  "fields": []
}
```

## Output

```json
{
  "query": {
    "label": "Query",
    "format": "string"
  },
  "name": {
    "label": "ENS name",
    "format": "string"
  },
  "address": {
    "label": "Address",
    "format": "string"
  },
  "isPrimaryName": {
    "label": "Is primary name",
    "format": "boolean"
  },
  "avatarUrl": {
    "label": "Avatar URL",
    "format": "string"
  },
  "twitter": {
    "label": "Twitter / X",
    "format": "string"
  },
  "github": {
    "label": "GitHub",
    "format": "string"
  },
  "url": {
    "label": "Website",
    "format": "string"
  },
  "flags": {
    "label": "Flags",
    "format": "array"
  },
  "completeness": {
    "label": "Profile completeness",
    "format": "number"
  }
}
```

## About this Actor

This example demonstrates how to use [ENS Resolver — Name to Address, Reverse Lookup, Avatar](https://apify.com/yadroo/ens-resolver.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/yadroo/ens-resolver.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/yadroo/ens-resolver.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).