AI / LLM Tooling

We’re building the infrastructure to make ENS a first-class citizen for AI agents.

The foundation for how developers and their AI agents reach for ENS is ensskills, that teach your AI assistant about ENS, ENSNode, the Omnigraph, and how to drive enscli—an agent- and human-friendly CLI—on your behalf.

Quickstart (`npm`/`pnpm`/`yarn`/`bun`)

Add ensskills and skills-npm to your project and wire a prepare script so the pinned skills re-sync into your agent directories (.claude/skills, .cursor/skills, …) on every install:

{
  "devDependencies": {
    "ensskills": "1.15.1",
    "skills-npm": "^1"
  },
  "scripts": {
    "prepare": "skills-npm"
  }
}

npm install   # symlinks the skills for your detected agents

Quickstart (`npx skills`)

Not in a Node project? skills installs every ENS skill straight from the repo, pinned to the matching release tag:

npx skills add https://github.com/namehash/ensnode/tree/v1.15.1/packages/ensskills/skills --skill '*'

Next Steps

That’s it—your AI agent now has all of ensskills at its disposal.

Which address currently owns vitalik.eth
and how many other domains do they own?

enscli An agent- and human-friendly CLI for the ENS Omnigraph API.

ensskills Skill bundles that give AI agents an opinionated contract for ENS.

Documentation as `llms.txt`

If you aren’t using ensskills, the entire documentation site is also published in the llms.txt format so any agent or LLM can load it directly as context:

/llms.txt — a structured index of the documentation with links to every page.
/llms-full.txt — the entire documentation concatenated into a single file, ready to drop into a model’s context window.

Paste this at the top of a prompt to point your agent at the full documentation before asking your question:

Load the ENSNode documentation from https://ensnode.io/llms-full.txt to answer the following question: