sales-skills/sales-namelix

Namelix Platform Help

Namelix (namelix.com) is a free, web-based AI business-name generator: you type in keywords and it returns short, brandable names (not random dictionary mashups) across styles like brandable, compound, and misspelled, with a randomness slider, free .com domain checks, and a paid path to a logo via its sister tool Brandmark. It's a fast idea-spark for founders, makers, and marketers — name generation is free with no account, and there's no documented public API (it's a UI tool; the only "APIs" are third-party scrapers).

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer:

1. What do you want from Namelix?
   • A) Get better name candidates out of it (styles, keywords, randomness)
   • B) Understand what's free vs paid (names/domains vs logo)
   • C) Decide if a generated name is worth registering (domain + trademark)
   • D) Automate/batch-generate names from a script
2. Have you validated the idea yet, or are you naming first?

Skip-ahead: if the user really wants the validate-before-building method or a tool comparison, this is a /sales-idea-validation question — route in Step 2.

Step 2 — Route or answer directly

| If the user's question is about… | Route to | |---|---| | Designing the logo / brand kit for the chosen name (Namelix's paid Brandmark hand-off) | /sales-brandmark {question} | | The validate-before-building method, or comparing naming/validation tools across the market | /sales-idea-validation {question} | | Growing a pre-launch waitlist / capturing signups on the new name | /sales-audience-growth {question} | | Building the landing page / smoke test under the new name | /sales-funnel {question} |

When routing, give the exact command: "This is a {domain} question — run: /sales-idea-validation {original question}"

Otherwise, answer Namelix-specific questions using Step 3.

Step 3 — Namelix platform reference

Read references/platform-guide.md for the full reference — the 8 naming styles and when each fits, the randomness slider, how the save-and-learn algorithm works, the free-names / free-domain-check / paid-Brandmark-logo boundary, best-effort logo pricing, keyword-phrasing recipes, and the no-public-API automation reality (including why the third-party pynamelix scrapers are unsupported).

Answer using only the relevant section — don't dump the full reference.

Step 4 — Actionable guidance

• Validate demand before you spend time naming. A name is downstream of a validated idea — if the user hasn't tested that anyone wants the thing, tell them naming is premature and route the go/no-go to /sales-idea-validation (a smoke test / pre-sale), then come back to name it.
• Drive quality with styles + keywords + the randomness slider, not luck. Feed it 1-3 concrete keywords, pick the style that matches the vibe (brandable like "Google" for abstract, compound like "FedEx" for descriptive, real-word for clarity), and turn randomness UP for more abstract/ inventive names or DOWN to stay close to the keywords. Save favorites — the algorithm biases later suggestions toward what you saved. Re-run variants.
• Names are free; the logo is the paywall. Generating names and checking .com availability cost nothing and need no account; the paid part is the Brandmark logo/brand package. Present logo pricing as best-effort (starts around a low-double-digit one-time fee) and tell the user to confirm current pricing on-site — don't pay for a logo before the name is locked.
• A free .com in Namelix is necessary, not sufficient — verify at a registrar and check the trademark. Namelix's inline check can lag; confirm availability at a registrar (and consider alt-TLDs) and do a basic USPTO/EUIPO trademark + social-handle check before committing, so you don't fall in love with a name you can't legally or practically own.
• Don't plan an integration around it — there's no public API. If asked to automate, say clearly there's no documented public API; the third-party pynamelix wrappers scrape the site and can break or get blocked without notice, so don't build on them. Generate in the UI, or use a service built for programmatic naming.

If you discover a gotcha or tip not in references/learnings.md, append it there with today's date.

Gotchas

Best-effort from research (2026-07) — pricing and features move; verify at namelix.com.

• Names are free; the logo is the monetization. Name generation and domain checks are free with no account — Namelix makes money on the paid Brandmark logo package, not the names.
• No documented public API. It's a UI tool. The community pynamelix libraries on PyPI/GitHub are unofficial scrapers — unsupported and prone to breaking when the site changes. Don't build on them.
• The domain check can be stale/optimistic — always re-verify a "free" .com at a real registrar and check other TLDs before you commit.
• A generated name is not a cleared name. Namelix doesn't do trademark or social-handle checks — run those yourself (USPTO/EUIPO + handle availability) before registering.
• Naming is downstream of validation. A great name for an unvalidated idea is wasted effort — test demand first (/sales-idea-validation).
• Output tracks input. Vague keywords → generic names; give it 1-3 sharp keywords, pick a style, and tune randomness. Brandmark (brandmark.io) is the sister logo tool, not a separate name generator.

Related skills

• /sales-brandmark — Namelix's paid sister tool: design the logo / brand kit once the name is locked (logo generation, tier choice, copyright/trademark)
• /sales-zoviz — A cheaper AI logo/brand-kit maker for the branding step (one-time logo pack ~$19.99, no Jack Qiao affiliation) — an alternative once the name is locked
• /sales-canva — Design the broader marketing/social creative and Brand Kit under the new name (templates, Content Planner, Connect API design automation)
• /sales-idea-validation — The tool-agnostic validate-before-building method and the full naming/validation landscape (validate before you name)
• /sales-audience-growth — Grow a pre-launch waitlist under the new name
• /sales-funnel — Build the smoke-test / landing page to test real demand for the newly named product
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: "Give me a good name for my idea"

User says: "I'm building an AI tool that turns meeting recordings into CRM notes — what should I call it?" Skill does: Suggests feeding Namelix 2-3 sharp keywords (e.g., "meeting", "notes", "CRM"), picking a brandable or compound style, and using the randomness slider to trade abstraction for clarity; notes names + .com checks are free, and flags that a name is downstream of validating anyone wants the tool — routing the go/no-go to /sales-idea-validation. Result: The founder gets a shortlist of ownable names and knows to validate demand before investing in branding.

Example 2: Free vs paid

User says: "Does Namelix cost anything? It's asking me to pay for a logo." Skill does: Explains name generation and domain-availability checks are free with no account, and the paid part is the Brandmark logo/brand package (best-effort ~low-double-digit one-time fee, confirm on-site); recommends locking the name first and only buying a logo once the name is final. Result: The user keeps generating names for free and avoids paying for a logo prematurely.

Example 3: Can I automate it via API? (developer/automation)

User says: "I want to batch-generate 200 names from a script — what's the Namelix API?" Skill does: States plainly there's no documented public API; notes the third-party pynamelix libraries on PyPI/GitHub are unofficial scrapers that can break or get blocked without notice and shouldn't be built on; suggests generating in the UI or using a tool designed for programmatic naming, and points to /sales-idea-validation for the broader landscape. Result: The user avoids building on an unsupported scraper and picks a workable path.

Troubleshooting

The names feel generic or off-brand

Symptom: Namelix keeps returning bland or irrelevant names. Cause: Vague keywords and a mismatched style; the default randomness may be too low or too high. Solution: Give it 1-3 concrete keywords, pick the style that matches the vibe (brandable vs compound vs real-word), adjust the randomness slider, and save the ones you like so the algorithm biases toward them. Re-run several variants.

The domain shows free but a registrar says it's taken

Symptom: Namelix marked a .com available, but it's registered elsewhere. Cause: The inline domain check can be cached or lag real registrar data. Solution: Always re-verify at a registrar before committing, consider alternate TLDs, and don't build around a name until the domain (and a basic trademark/handle check) clears.

"Is there an API?" / my automation broke

Symptom: Can't find API docs, or a script using pynamelix stopped working. Cause: There's no official public API; pynamelix and similar libraries scrape the live site and break when it changes. Solution: Don't rely on scrapers for anything durable. Generate names in the UI, or use a service intended for programmatic naming. See /sales-idea-validation for options.