Frequently asked questions

A good API name is short, pronounceable, and spellable after hearing it once. It hints at the domain without boxing you into a single feature, and it survives trademark and domain checks. Our naming guide walks through the full selection process.

Including "API" adds clarity on directories, docs and search results — nobody wonders what the product is. Dropping it makes the name more brandable as a standalone product. Many teams use the bare name as the brand and add "API" in titles and metadata only.

No. ApiAlias generates combinations without checking trademarks, existing products or domains. Always search your country's trademark database and check domain availability before using a name commercially.

The word lists and patterns are tuned for developer tools: short compound blends, technical vocabulary, and domain nouns developers search for (auth, billing, webhooks). Generic business generators optimize for a different audience.

As a starting point, yes — but it is only a candidate until cleared. Run the trademark, domain and package-availability checks first, and search the exact name in quotes for existing products.

Yes. It runs entirely in your browser using crypto.getRandomValues(). Seed words and generated names never leave your device. See the privacy page.

The seed word is a word from your API's domain — payments, maps, weather. When set, some generated names are built around it, so the shortlist stays relevant to what you are building instead of drifting into generic tech words.

Compound (SyncForge) reads like a startup and is the most brandable. Two-word (Swift Payments) is clearer and better for search. Descriptive (Nexus for Analytics) suits internal platforms. Try all three on the same seed word and compare.

One or two words, ideally under 15 characters. Short names survive spoken conversation, fit in package names and URLs, and are easier to trademark-search.

Treat the trademark search as the gate and domains as logistics. A taken domain has workarounds (different TLD, a short prefix); a conflicting trademark can force a full rename after launch.

Check the trademark first — if that conflicts, move on. If only the domain is taken, a clean alternative TLD, a short prefix like get-, or a slight variation can work. Never build a brand while a squatter holds the exact .com in your category.

You can, but it is expensive: domains, packages, docs, SDKs, webhooks and customer integrations all move. An extra week on the name now is cheaper than a rename in year two.

A seed word is a word from your API's domain — payments, maps, weather. When you type one into the generator, some names are built around it so the shortlist stays relevant to what you are building instead of drifting into generic tech vocabulary. It is optional: without it you get broader, more surprising combinations.