Sessions for people
The browser uses the signed-in Clerk session. Users never copy a secret into the web app.
Public docs · protected execution
One account for every naming workflow.
Create revocable keys for agents and scripts, see exactly how credits are used, and keep the API contract public for people and search engines.
Free developer account10,000 credits / month
REST · CLI · MCP · browser session
Loading your developer account…
Fastest setup
Paste one instruction into Codex or Claude
Use NamingSignal for this naming task. First read https://namingsignal.com/agent-guide.txt and https://namingsignal.com/openapi.json. Use https://namingsignal.com/api/v1/health for public service discovery. For protected REST calls, read NAMING_SIGNAL_API_KEY from the local environment and send it as "Authorization: Bearer $NAMING_SIGNAL_API_KEY"; never print, log, commit, or ask me to paste the secret into chat. If the variable is missing, ask me to create a free key at https://namingsignal.com/developers/keys and set it locally. Use one unique Idempotency-Key per logical POST and one X-Name-Ledger-Sprint value across a sprint. For feedback rounds, pass the founder's instruction plus likedNames and dislikedNames in generate.iteration, and pass the complete prior ledger in excludedNames. Preserve the complete evidence ledger, uncertainty, sources, timestamps, feedback rounds, usage, and quota data. Never describe RDAP not-found as guaranteed availability and never claim trademark clearance.Keys for tools
REST, CLI, and stdio MCP read a separately revocable user key from the local environment.
Evidence in every result
Source, time, state, confidence, and honest unknowns travel with each domain or namespace claim.