One API · One Key

Domain Data & WHOIS API: REST, SDKs, CLI and n8n.

Query 6 domain lifecycle databases (NRDs, Active, Aged, Expired, Deleted, Marketplace), run live RDAP WHOIS and DNS lookups, and pull registration trends, all with a single Bearer API key.

REST API

Every endpoint over HTTPS with a Bearer key. OpenAPI spec included.

SDKs

Python (domainkits on PyPI), TypeScript (@domainkits/sdk on npm) and Go. Automatic paging, structured quota errors.

n8n Node

n8n-nodes-domainkits puts domain search in your workflows, usable by n8n AI agents as a tool.

CLI

dk is a single binary for macOS, Linux and Windows. Search, WHOIS, DNS and trends from your terminal.

Pick Your Surface, Keep One Key

The same key authenticates every surface. Start with whichever fits your stack; switching later costs nothing because they all speak to the same API.

REST
curl "https://premium-api.domainkits.com/api/v1/search/expired?query=clinic&tld=com" \
  -H "Authorization: Bearer dk_xxx"
API reference
Python SDK
pip install domainkits

dk = DomainKits("dk_xxx")
dk.expired.list(query="clinic", tld="com")
domainkits on PyPI
TypeScript SDK
npm install @domainkits/sdk

const dk = new DomainKits('dk_xxx');
await dk.expired.list({ query: 'clinic', tld: 'com' });
@domainkits/sdk on npm
Go SDK
go get github.com/ABTdomain/domainkits-sdk-go

dk := domainkits.New("dk_xxx")
dk.Expired(ctx, domainkits.Params{"query": "clinic", "tld": "com"})
domainkits-sdk-go on GitHub
n8n Node
Settings > Community Nodes > Install
n8n-nodes-domainkits

One credential covers every resource.
n8n-nodes-domainkits on npm
CLI
go install github.com/ABTdomain/domainkits-cli/cmd/dk@latest

export DOMAINKITS_API_KEY=dk_xxx
$env:DOMAINKITS_API_KEY="dk_xxx"   (PowerShell)
dk search expired query=clinic tld=com
domainkits-cli on GitHub

Domain Data from the Command Line

dk brings the API to your terminal and shell scripts. Run searches, WHOIS lookups (one domain or a list), DNS lookups and reverse nameserver checks, pull registration trends, and fetch the daily newly registered domain files. Parameters pass straight through to the API, so the filters in the API reference work as documented.

Responses print as JSON, ready to pipe into other tools, and export=csv saves a file instead. Exit codes separate API errors from usage and network errors, which keeps cron jobs and CI scripts simple. Prebuilt binaries for macOS, Linux and Windows are on GitHub, or install with Go. The CLI is open source under the MIT license and uses your API key, so it works on Premium and higher plans.

A Domain Data API Built Around Research

The core of the API is research: query six domain inventories by keyword, or browse an entire gTLD, then stack filters for length, age, composition and sale status until millions of names narrow down to a decision-ready shortlist.

From there the endpoints chain together. A typical flow: search a keyword across newly registered domains, check WHOIS and DNS on the interesting ones, confirm how the keyword is trending, then see whether matching names are listed for sale.

  • Search: newly registered, aged, active, expired, deleted and for-sale domains.
  • Lookups: WHOIS, DNS, reverse nameserver, IP geolocation, registrar and EPP status checks, answered at request time.
  • Trends: daily registration volumes per gTLD with moving averages, and hot, emerging and prefix keyword rankings.
  • Downloads: daily newly registered domain files by TLD.
  • Account: per-endpoint usage counters, so quota checks can be automated.
6
Domain databases, from NRDs to deleted and for-sale domains
Live
WHOIS, DNS and reverse NS lookups at request time
4
Ways to connect: REST, SDKs, CLI and n8n
No PII
We do not collect or share registrant data

Frequently Asked Questions

What endpoints are included in the DomainKits Domain API?

A single API key unlocks five endpoint groups designed to chain together in automated pipelines:

How can I connect: REST API, SDKs, CLI, or n8n?

Every surface authenticates with the same API key (dk_xxx), so you can mix and match tools across your stack:

  • REST API (HTTPS and OpenAPI): standard JSON endpoints you can call from any language or curl, with an OpenAPI specification. See the API reference.
  • Python, TypeScript, and Go SDKs: pip install domainkits, @domainkits/sdk on npm, and domainkits-sdk-go, with automatic pagination and structured quota errors.
  • Command-line client (dk): an open-source (MIT) single binary for macOS, Linux, and Windows. Pipe JSON responses into jq, pass export=csv to save a file, and rely on exit codes for cron jobs and CI scripts.
  • n8n community node (n8n-nodes-domainkits): drop domain search, WHOIS, and trend lookups into n8n workflows, or expose them as tools for n8n AI agents.

What is the TLD coverage, update cadence, and privacy policy?

  • Coverage: NRD, active, and marketplace search cover gTLDs plus 147 country-code TLDs on Premium, including second-level suffixes such as com.br. The other searches and the registration trends cover gTLDs.
  • Cadence: NRD search is refreshed throughout the day, and WHOIS, DNS, and reverse nameserver lookups run live at request time. Trend windows span 7 to 180 days.
  • No personal data: WHOIS results are limited to registrar, dates, EPP status codes, and nameservers; registrant names, emails, addresses, and phone numbers are not returned. In line with GDPR, we do not collect or share registrant data.

Should I use the REST API or the DomainKits MCP Server for AI agents?

DomainKits supports both deterministic code pipelines and conversational AI agents:

  • Use the Developer API (this page): when you build production backend services, automated cron pipelines, brand monitoring or threat-hunting scripts, portfolio dashboards, or n8n workflows that need strict schema control and dedicated API quotas.
  • Use the DomainKits MCP Server and Agent Skills: when you want AI assistants such as Claude, ChatGPT, Cursor, or Gemini CLI to query domain data and run multi-step consultations in plain language.

Which plans include API access, and how does quota metering work?

  • Plan requirement: the REST API, the SDKs, the dk CLI, and the n8n node are included with Premium and higher plans. See pricing to compare plans.
  • Separate API quota: API usage is metered separately from your web limits, so scripts and cron jobs do not consume the quotas you use on the site. Every response carries rate-limit headers, and per-endpoint limits are listed in the API reference (sign in required).