# NamingSignal

> Evidence-first product naming for founders and developer agents. NamingSignal compiles a sentence, prompt, README, or safe public page into an editable brief; generates 100-200 names across public creative directions; checks selected domain endings; ranks registry survivors; and supports source-backed finalist research. Registry RDAP not-found is described as likely unregistered, never as guaranteed registrable. Trademark output is preliminary research, not legal clearance.

## Tools

- [NamingSignal web application](https://namingsignal.com/): the full naming sprint: brief, generation, domain evidence, ranking, and research
- [Product name generator](https://namingsignal.com/product-name-generator): generate product names with collision evidence and explicit uncertainty
- [App name generator](https://namingsignal.com/app-name-generator): app names with app, domain, and namespace checks
- [Project name generator](https://namingsignal.com/project-name-generator): name a project from a brief or README
- [SaaS name generator](https://namingsignal.com/saas-name-generator): SaaS names with software collision context
- [Brand name tester](https://namingsignal.com/brand-name-tester): test one brand name with explainable risks
- [Domain name checker](https://namingsignal.com/domain-name-checker): single-name domain and namespace checks with sources and timestamps

## Developers and agents

- [Domain availability API overview](https://namingsignal.com/domain-availability-api): the authenticated REST API for domain evidence
- [Developer console](https://namingsignal.com/developers): create and revoke user-owned API keys
- [REST, CLI, and MCP documentation](https://namingsignal.com/developers/docs): the complete public surface reference
- [Agent workflow guide](https://namingsignal.com/agent-guide.txt): plain-text sequencing, evidence semantics, and batch limits for agents
- [OpenAPI 3.1 description](https://namingsignal.com/openapi.json): machine-readable REST contract
- [Provider readiness and limits](https://namingsignal.com/api/v1/health): public health route with the current credit allowance and operation schedule
- [Full machine-readable overview](https://namingsignal.com/llms-full.txt): expanded product, API, CLI, and MCP reference in one file

REST routes: POST /api/v1/brief, /api/v1/generate, /api/v1/check, /api/v1/rank, /api/v1/research; GET /api/v1/health. The health route and all documentation are public. Every POST requires a signed-in Clerk session or a user-owned NamingSignal API key sent as an Authorization Bearer token. CLI and stdio MCP clients read NAMING_SIGNAL_API_KEY from the local environment. Never put the key in a URL, prompt, repository, or log. Free accounts receive a monthly Naming Credits allowance; the machine-readable amount and operation conversion schedule are published by /api/v1/health.

## Research and guides

- [Why Domain Availability Is Not a Boolean](https://namingsignal.com/blog/domain-availability-is-not-a-boolean): A 404 from a domain lookup is not proof a name is free. How registry evidence, known-registered canaries, and calibration keep false positives out.
- [The Evidence-First Product Naming Workflow](https://namingsignal.com/blog/evidence-first-product-naming-workflow): A practical naming workflow: compile the brief, generate a broad field, check domain evidence, keep blockers visible, and research up to three finalists.
- [How to Name a Project from Its README with Codex or Claude](https://namingsignal.com/blog/name-a-project-from-readme-with-ai-agent): A bounded agent workflow for turning a README into a naming brief, generating project names, checking domains and namespaces, and exporting the decision.
- [How to Name an App People Can Find and Say](https://namingsignal.com/blog/how-to-name-an-app): A practical app-naming checklist for product fit, spoken recall, app-store collisions, domains, developer namespaces, and final selection.
- [How to Name a SaaS Product Without Boxing It In](https://namingsignal.com/blog/how-to-name-a-saas-product): A focused SaaS naming method for category fit, brand width, domain checks, software collisions, and a shortlist that can survive product expansion.
- [How to Check a Product Name Before Launch](https://namingsignal.com/blog/how-to-check-a-product-name-before-launch): A pre-launch checklist: same-category collisions, domain evidence, app and developer namespaces, spoken-name failures, and preliminary trademark research.

## Policies

- [Privacy policy](https://namingsignal.com/privacy): what is stored, what is excluded from analytics, and retention
- [Terms of service](https://namingsignal.com/terms): service terms and acceptable use
- [Security](https://namingsignal.com/security): security posture and reporting
- [Disclosures](https://namingsignal.com/disclosures): product and commercial disclosures

These pages are written for human and agent retrieval. They distinguish registry evidence from registrar checkout, scores from hard blockers, preliminary collision research from legal clearance, and generated output from deterministic fallback.