Skip to content

ENSNode Quickstart

Use this page to choose the fastest path for your ENSNode use case: quick testing, app integration, raw API usage, or self-hosting.

The fastest way to query ENSNode is to use the NameHash Labs hosted instances of ENSNode. The alpha instance provides support for mainnet, base.eth, linea.eth, and 3DNS ENS names.

https://api.alpha.ensnode.io

Developers use ENSNode in different ways depending on their goals. Pick the path that best matches your use case:

Choose this if you want the fastest hands-on start with no local setup. This guide shows available hosted endpoints, what each deployment is used for, and how to connect them to ENSAdmin for quick exploration and validation.

Choose this if you need graphql API access and want to build directly against API responses. This guide will cover endpoints, response shapes, and integration patterns for backend services and data pipelines.

Choose this if you prefer a typed SDK experience for app integration. This guide will cover SDK setup, common query patterns, and recommended usage for production applications.

Choose this if your app already uses ensjs and you want minimal migration effort. This guide explains how to point ensjs to ENSNode’s subgraph-compatible endpoint and keep familiar ensjs query workflows.

Choose this if you are building UI-heavy apps and want reusable ENS-focused components/hooks. This guide will cover how to wire ENSNode-backed data into frontend flows with minimal boilerplate.

Choose this if your tooling expects ENS endpoints via viem chain configuration. This guide explains how to configure viem/chain objects so ENS-aware libraries can consume ENSNode seamlessly.

Choose this if you need production ownership of uptime, data freshness strategy, and infrastructure. This guide compares deployment options (Docker, Render, Terraform) and links to the setup steps for each path.