Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,30 @@ The Omnigraph API is a GraphQL API following the Relay specification, so you get
title='Omnigraph GraphQL API Documentation'
href="/docs/integrate/integration-options/omnigraph-graphql-api"
/>

## 4. `ENSDb`

For special use cases that go beyond what the ENS Omnigraph exposes, query the live state of ENSv2 directly via SQL. `ENSDb` stores ENS state in a PostgreSQL database — usable from any language with a Postgres driver.

<LinkCard
title='ENSDb Integration Documentation'
href="/docs/integrate/integration-options/ensdb"
/>

Comment thread
sevenzing marked this conversation as resolved.
## 5. `enscli`

`enscli` is a CLI that wraps `enssdk` to bring the ENS Omnigraph to the terminal. Designed for developers exploring or validating integrations, operators wiring ENS lookups into shell pipelines, and AI coding agents driving `ensskills`.

<LinkCard
title='enscli Integration Documentation'
href="/docs/integrate/integration-options/enscli"
/>

## 6. `ensskills`

`ensskills` is a collection of curated skill bundles that give AI coding agents a well-defined contract for working with ENS — powering conversational ENS lookups and streamlining integration code written with `enskit`, `enssdk`, or the raw Omnigraph API.

<LinkCard
title='ensskills Integration Documentation'
href="/docs/integrate/integration-options/ensskills"
/>
Comment thread
sevenzing marked this conversation as resolved.
Loading