A fast, agent-friendly command-line tool for Name.com DNS and domains, built on the current v4 API.
- a
--json
everywherecommands
introspection command, so AI agents can discover and drive the whole surfaceIdempotent(create-or-update, never duplicate) — the right primitive for automation and IaCrecords set
Secure auth— credentials live in the macOS Keychain (or a0600
config file), never in your shell environmentZero native dependencies— just Node 20+ and a few small pure-JS deps (commander
,@clack/prompts
,picocolors
)
Why this exists: the only prior community tool (
namedns
) has been unmaintained since 2018 and targets Name.com's dead v1 reseller API.namecom-cli
uses the current v4 API and is designed to be driven by humans and agents alike.
npx namecom-cli --help
npm install -g namecom-cli
namecom --help
This repo ships a Claude/Codex skill that teaches an agent to drive the CLI. The CLI can install its own skill:
namecom skill install --agent claude-code # or: --agent codex
namecom skill path # prints the bundled SKILL.md for manual/offline install
…or use the official skills CLI directly:
npx skills add hypersocialinc/namecom-cli --skill namecom --agent claude-code
The skill is written to work zero-install — it calls npx namecom-cli
when the
namecom
binary isn't on PATH — so adding only the skill still works.
Create a production API token at https://www.name.com/account/settings/api (you get a username + token), then:
namecom login # prompts for username + token (masked) at a TTY;
namecom login --user <username> --token <token># or pass them directly / via env
Interactive only for humans.Prompts, spinners, and color appear only when you're at a real terminal. When output is piped, in CI, an agent is driving, or you pass--json
, the CLI is fully non-interactive and deterministic — missing inputs become a clean error, never a hung prompt. (namecom
andnamecom-cli
are both valid commands.)
login
verifies the credentials, then stores them in your macOS Keychain (namecom_user
/ namecom_token
). You can also just set NAMECOM_USER
/ NAMECOM_TOKEN
in the environment and skip login
.
Resolution order on every command: --user/--token
flags → env vars → Keychain → ~/.config/namecom/credentials.json
.
namecom whoami # verify auth, show domain count
namecom domains list # list every domain in the account
namecom records list example.com # all records
namecom records list example.com --type TXT # filter by type
namecom records list example.com --host send # filter by host
namecom records create example.com --host www --type CNAME --answer example.vercel.app
namecom records update example.com 12345 --ttl 600
namecom records delete example.com 12345
namecom records set example.com --host send --type MX \
--answer feedback-smtp.us-east-1.amazonses.com --priority 10
Add --json
to any command for machine-readable output, and --api-url https://api.dev.name.com
to target the sandbox.
namecom records set example.com --host 'resend._domainkey.mail' --type TXT --answer 'p=MIGf...'
namecom records set example.com --host 'send.mail' --type MX --answer 'feedback-smtp.us-east-1.amazonses.com' --priority 10
namecom records set example.com --host 'send.mail' --type TXT --answer 'v=spf1 include:amazonses.com ~all'
namecom commands # full command tree as JSON
namecom <cmd> --json # structured output for any command
@
means the zone apex (root). Hosts are relative to the domain (e.g. host send
on example.com
→ send.example.com
).
- Scope is
DNS records(
list/get/create/update/delete/set
) and read-only.domains list
- Not (yet) covered: nameservers, URL forwarding, domain registration/transfer/contacts. The
client/
layer is kept separate from commands so these are easy to add. - This is an unofficial tool and is not affiliated with Name.com.
namecom-cli
is v1 of a provider-agnostic "agents can do DNS" tool. The
registrar API (src/client.js
) is a separate layer from the commands, so adding another provider is a small, well-scoped contribution.
Wanted — help expand it to more registrars:
- Cloudflare
- AWS Route 53
- Porkbun
- Namecheap
If "agents that can do DNS" should work for your registrar, come build it — see good first issues and CONTRIBUTING.md (it documents the provider interface).
MIT © Hypersocial, Inc.