Superhero Name Generator API

About the Superhero Name Generator API

A superhero name generator API that returns one hero or villain name per call, assembled from templates and themed word lists. Comic book creators, game developers, creative writers, and anyone needing heroic alter-egos can drop it into a character builder, a username suggestion step, a tabletop session or a party game.

You can leave the style open or choose one of six: dark, cosmic, elemental, tech, heroic or mystic. Each style has its own templates and vocabulary, so a dark name comes out sounding like Lord Stalker rather than a bright, classic champion. Call it several times to offer a shortlist and let the user pick the one they like.

The response is deliberately small: the generated name and the style that was requested. There are no premium-only fields, so the Free plan returns exactly the same data as paid plans, which makes it easy to prototype a name picker or a random hero button and keep the same integration as usage grows.

How it works

Each call picks a style, then one of that style's templates, then fills the template's named placeholders with random words. Every placeholder is replaced by a random entry from the style's word list for that placeholder type. If the style has no words for a placeholder, the shared common word list is used instead. Templates and word lists are loaded from a data file and cached in memory.

style is lowercased before use and must be one of dark, cosmic, elemental, tech, heroic or mystic; other values are rejected by validation. With no style, one is drawn at random from the available styles.

name is the finished name. style in the response is the style you requested, or the literal string random when you sent none, even though a specific style was used internally to build the name. If you need to know which style produced a name, pass the style explicitly.

Names are not checked for uniqueness or against existing characters and trademarks, and the same name can come back on separate calls, more often within a single style. If you need distinct names across calls, keep a record of the ones you have already issued and request again on a repeat. Both fields are returned on every plan.

What people use it for

Game Development

Generate hero names for RPGs and superhero games

Creative Writing

Find names for comic book or novel characters

Team Building

Create fun superhero personas for team activities

Entertainment

Generate amusing hero names for party games

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/superheroname

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Optional

1
2

curl "https://api.apiverve.com/v1/superheroname?style=dark" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/superheroname

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8

{
  "status": "ok",
  "error": null,
  "data": {
    "name": "Lord Stalker",
    "style": "dark"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 1 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Superhero Name Generator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Superhero Name Generator API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1