Name ideas
Describe what you are naming, a product, a coffee brand or a podcast, and get a batch of candidates to react to, built on different naming strategies rather than synonyms. Reacting to twenty options beats inventing the first one from nothing. You pay per use, with no subscription.
Run it online
Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.
Naming something new is disproportionately hard for how small the deliverable looks — a good name has to sound right out loud, read cleanly on a screen, and still have a domain worth registering.
Why naming stalls more than other decisions
A product spec can be wrong and fixed in the next sprint; a name gets printed on business cards, baked into a domain and repeated by customers for years. That asymmetry is why founders and product teams stall on naming longer than on almost any other decision. A good name has to sound right out loud, read cleanly on a screen and still have a domain worth registering, which is a lot to ask of one or two words. This tool shortens the stall by handing you a real batch to react to, because choosing among twenty options is a far easier task than producing the first one from nothing.
Naming strategies, not synonyms
Company and product names have gone through recognizable eras: the literal descriptive names of the industrial age, the founder surnames of the early twentieth century, the invented words that Kodak and Exxon made popular because a new word could be trademarked cleanly, and later the compound and blended names. The batch draws on different strategies like these instead of shuffling synonyms of your keywords. A founder can shortlist candidates before buying a domain, a marketing team can explore directions when an old brand is retired, and a creator can name a podcast and then test it against the domains and handles still available.
What you can do with it
New SaaS product launch
A founder describes the product's core function and gets a batch of name candidates to shortlist before committing to a domain purchase.
Rebrand exploration
A marketing team generates a fresh batch of naming directions when an existing brand name is being retired, without starting from a blank whiteboard.
Side project or podcast naming
An indie creator describes their podcast concept and gets a batch of names to test against available domains and handles.
FAQ
What naming styles does it generate?
A single batch mixes descriptive, evocative, invented and compound-word approaches so you can compare styles instead of only seeing variations on one idea.
What happens if a naming task fails?
Failed tasks are retried automatically up to three times; if none succeed you get a clear error and pay nothing for that task.
What do I need to describe to get name ideas?
A short description of what you are naming and what it does is enough: a software product, a coffee brand, a podcast or a legal entity. The batch is then built around different naming strategies, not around synonyms of your keywords.
What should I check before choosing a name from the batch?
Shortlist a few and check each one yourself: say it out loud, read it on a screen, and find out whether a domain and social handles worth having are still available before you commit to it.
Can it help when we are renaming an existing brand?
Yes. When an existing brand name is being retired, a marketing team can generate a fresh batch of naming directions to explore, instead of starting the discussion from a blank whiteboard.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/text/name-ideas \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}'const res = await fetch("https://api.kit.forhosting.com/text/name-ideas", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/text/name-ideas",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/text/name-ideas", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/text/name-ideas", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "text.name_ideas",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_tokens | 20000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
422 | task_failed | The task failed after 3 retries. You are never charged for it. |
Technical notes
This endpoint takes a short description of what you're naming and returns a batch of candidates built around different naming strategies, not just synonyms of your keywords.
Why naming is its own category of hard
A product spec can be wrong and fixed in the next sprint; a name gets printed on business cards, baked into a domain, and repeated by customers for years. That asymmetry is why founders and product teams stall out on naming longer than almost any other decision. text.name_ideas shortens that stall by giving you a real batch to react to — reacting to twenty options is a much easier cognitive task than generating the first one from nothing.
The mechanics of a request
Nothing about the naming process requires you to keep a connection open while the model works. You describe what you're naming — a SaaS product, a coffee brand, a podcast, a legal entity — and POST it to /text/name-ideas. The call returns a task_id immediately and processes in the background; the finished batch arrives at your webhook or waits at a signed link for 24 hours.
Where naming conventions actually come from
Company and product naming has cycled through recognizable eras — the literal descriptive names of the industrial age, the founder-surname era of the early twentieth century, the invented-word wave that Kodak and Exxon popularized specifically because a novel word could be trademarked cleanly, and the compound and portmanteau style common in software today. The endpoint draws on several of these strategies at once within a single batch, rather than locking you into one aesthetic.
What the batch actually contains
Each batch mixes different naming approaches — descriptive, evocative, invented, compound — so you're not just seeing twenty variations on one idea. Results are generated from what you tell us about the product; the endpoint doesn't check live domain or trademark availability, so treat the batch as a shortlist to verify yourself before you commit to registering anything.
Fitting naming into a product workflow
Because it's async and webhook-driven, this slots naturally into an internal tool that lets a team vote on a shortlist, a startup incubator's intake form, or a script that runs alongside domain-availability checks so you only review names that are actually registrable. Pair it with the slogan endpoint once the name is locked in and you need a tagline to go with it.
Integration use cases
Client naming deliverable
A branding agency uses the endpoint to produce a first-pass batch of name options for a client brief before their own creative review.
Technical questions
How does the business name generator API work?
You POST a short description of your product, brand or company to /text/name-ideas, get a task_id back right away, and receive the full batch of name ideas by webhook or a signed 24-hour link once it's ready.
Is the name generator API free to use?
There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.
Does it check if the domain name is available?
No, the endpoint generates name ideas based on your description only; it doesn't check live domain or trademark availability, so verify any candidate before registering it.
How many names come back in one batch?
You get one priced batch per request containing multiple name candidates spanning different naming styles, from descriptive to invented words.
Can I use it for company names, not just product names?
Yes, describe the entity you're naming — company, product, brand or project — and the endpoint adapts the batch to that context.
Can I generate name batches in bulk for multiple projects?
Yes, since each request returns a task_id immediately, you can queue a batch per project and collect every result as its webhook arrives.