namehunt

Naming a company usually goes: generate names, check domains, find everything taken, start over. namehunt closes that loop in one CLI — an LLM proposes names from your brief, RDAP checks live availability on your TLDs, and the results plus your feedback steer the next round.

$ namehunt run --brief brief.md --tlds com,ai

 round 2 — 20 new candidates
┏━━━┳━━━━━━━━━┳━━━━━━┳━━━━━┓
┃ # ┃ name    ┃ .com ┃ .ai ┃
┡━━━╇━━━━━━━━━╇━━━━━━╇━━━━━┩
│ 1 │ vesper  │  ❌  │ ❌  │
│ 2 │ corvid  │  ❌  │ ❌  │
│ 3 │ prescry │  ✅  │ ✅  │
└───┴─────────┴──────┴─────┘
[a]nother round  [l]ike <numbers>  [d]islike <numbers>  [n]ote <text>  [q]uit & export

Works with an Anthropic or OpenAI API key — or with no key at all, using your existing Claude Code or Codex CLI login.

Quickstart

Needs uv. Write a few lines about your project, then run:

printf 'CLI that turns messy CSVs into typed parquet.\nFor data engineers. Vibe: short, unix-y.\n' > brief.md
uvx namehunt run --brief brief.md --provider claudecode --tlds com,ai

(No Claude Code? Use --provider claude with ANTHROPIC_API_KEY exported.)

Each round prints the table, then asks for feedback:

• l 2 5 / d 3 — like / dislike rows, steers the next round
• n shorter, more mythic — free-text steering note
• a — another round, q — quit

Ctrl-C is always safe; state is saved after every round.

uvx namehunt resume --session default               # pick up where you left off
uvx namehunt export --session default --format md   # or csv, json

Useful flags: --batch 20 names per round, --rounds 3 to run unattended, --style "short, mythic", --session <name> for parallel hunts, --debug to print the outgoing LLM prompt. Permanent install: uv tool install namehunt.

Providers

The CLI providers run claude -p / codex exec (sandboxed read-only) as subprocesses and strip API keys from their environment, so they can never silently bill an API. Subscription login is for personal use — don't ship a product on it (Anthropic's policy).

NAMEHUNT_PROVIDER sets the default provider; NAMEHUNT_HOME moves the state dir (default ~/.namehunt). Keys are read from the environment and never written to disk.

How availability works

• ✅ available — the registry's RDAP says the domain doesn't exist
• ❌ taken — RDAP returned a registration
• ❓ unknown — the check failed (timeout, rate limit, or a TLD without RDAP, like .io). Never treated as available.

RDAP "available" is a strong signal, not a guarantee: premium and reserved names can still be unregisterable. Re-check at your registrar and run a trademark search before you fall in love.

Development

git clone https://github.com/Tarabcak/namehunt && cd namehunt && uv sync
uv run pytest -q                     # all network mocked; suite blocks real sockets
uv run ruff check . && uv run mypy src

Built spec-first with strict TDD by Claude Code; the spec, workflow rules and hooks are in the repo (namehunt-SPEC.md, CLAUDE.md). Every RDAP failure path is tested to map to unknown, never available.