Fungenerators Name Generation API
Browse all Fungenerators APIsOfficial vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer2 EndpointsREST
For Agents
Generate random names from many themed categories such as fantasy characters, brands, screen names, and pet names.
Use for: Generate a random fantasy character name, List all the supported name categories, Find a screen name idea for a new gaming account, Get five baby name suggestions in one category
Not supported: Does not validate, register, or check trademark availability for names - use for generating themed random name suggestions only.
The Name Generation API produces random names tailored to a chosen category, covering use cases from fictional characters to product names, brands, screen names, baby names, and themed identities. Two endpoints are available: one to list supported categories and one to generate a name within a chosen category. The API is intended for game studios, novelty apps, marketing tooling, and creative workflows that need on-demand naming variety. Returns are short string lists, easy to integrate with chat UIs, design tools, and agent workflows.
Install Jentic One Beta
Connect the Name Generation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Name Generation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffungenerators.com%2Ffungenerators-namegen" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffungenerators.com%2Ffungenerators-namegen" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Name Generation API.
Generate a random name within a chosen themed category
List every supported name category for selection menus
Produce batches of fictional character names for game and story tools
Suggest brand and product name candidates for marketing prototypes
Surface screen-name and gamertag ideas for community apps
Use Cases
Patterns agents use Name Generation API for, with concrete tasks.
★ Character Name Generation for Games and Stories
Game developers and writers need a steady supply of names with the right thematic flavour. The Name Generation API exposes hundreds of categories and returns a fresh name per call, so studios can plug it into character creators, NPC populators, or writing assistants without building bespoke name dictionaries.
Call GET /name/categories, pick category=fantasy, then call GET /name/generate with that category five times to populate an NPC roster.
Brand and Product Name Brainstorming
Product and marketing teams use the API to seed brainstorming sessions with random brand-style names. By selecting brand or product categories the team gets dozens of candidates per session, then filters them against availability and trademark checks. The API does not rank names - it supplies raw variety.
Generate ten name candidates from category=brand and write them to a shared doc for the team to evaluate.
Screen Names and Gamertag Suggestions
Community platforms suggest screen-name candidates when a user's first choice is taken. The API returns themed alternatives that match the platform's vibe, such as gamertag-style or fantasy-style names. The integration is two calls: list categories once, then generate on demand inside the signup flow.
When a username is taken, call GET /name/generate with category=gamertag and propose three alternatives to the user.
AI Agent Naming Helper
Wire the Name Generation API into a Jentic-managed tool so agents can answer requests like 'suggest a fantasy tavern name' or 'give me ten cyberpunk handles'. The agent uses Jentic's intent search to find the right operation, then executes it without handling the bearer token. This is a low-friction creative tool for chat assistants.
Use Jentic to search 'generate a random themed name', load GET /name/generate, and execute it with the user's chosen category.
Key Endpoints
2 endpoints — the name generation api produces random names tailored to a chosen category, covering use cases from fictional characters to product names, brands, screen names, baby names, and themed identities.
METHOD
PATH
DESCRIPTION
GET
/name/generate
Generate a random name in a chosen category
GET
/name/categories
List all supported name categories
GET
/name/generate
Generate a random name in a chosen category
GET
/name/categories
List all supported name categories
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fungenerators Name Generation API by hand means passing your API key as a bearer token in the Authorization header on api.fungenerators.com and reading the categories route to know which themes are valid. Through Jentic you install once, import the Name Generation API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Name Generation API takes its input in query parameters rather than a resource path, so you limit the agent to the operations it needs, such as generating a name or listing categories. You choose which operations it may call, and nothing outside that set runs.
Credential isolation
Your Fungenerators token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate a random themed name' or 'list name categories', and Jentic returns the matching GET /name/generate or GET /name/categories operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Name Generation API through Jentic.
What authentication does the Name Generation API use?
It uses HTTP bearer token authentication. Through Jentic the token is held encrypted and injected at runtime, so the agent context never sees the raw secret.
Can I generate fantasy or brand names with this API?
Yes. Call GET /name/categories to discover the available category keys, then call GET /name/generate with the chosen category to get a name in that style.
What are the rate limits for the Name Generation API?
The OpenAPI spec does not declare explicit rate limits. Fungenerators applies plan-based quotas via subscription tiers on fungenerators.com, so check the tier you signed up for to see the per-minute and per-day caps.
How do I generate a random name through Jentic?
Search 'generate a random themed name' via the Jentic SDK or MCP server, load the GET /name/generate operation schema, and execute it with the category parameter. Install with pip install jentic and authenticate with your ak_* key.
How many names can I generate per call?
The generate endpoint returns a single name per call. To get a batch, loop the call N times in your client. The categories endpoint is a one-shot lookup that you can cache.
Can I add my own categories to the Name Generation API?
No. The category list is fixed by Fungenerators and only modifiable by them. You can call GET /name/categories at any time to see what is currently available.
Can I limit what my agent is allowed to do with the Name Generation API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use, and you can allow only the calls it needs, such as GET /name/generate for creating a name or GET /name/categories for listing the supported themes. The API takes its input through query parameters rather than a resource path, so scoping it to one or both of these read-only operations is straightforward and nothing outside that set runs. You also store the bearer token once in your own instance, and it is injected at execution time so it never reaches the agent's prompt or logs.
GET STARTED