Game Character Generator API

About the Game Character Generator API

A random RPG character generator for tabletop campaigns, game prototypes and roleplay prompts. Each call returns a ready-to-play fantasy character: a name that fits the race, the race and its traits, a class with its role and primary ability, six ability scores with modifiers rolled the D&D way on 3d6, starting hit points, a personality trait and a motivation.

You can fix the race, the class or both, choosing from ten races such as Elf, Dwarf, Tiefling and Dragonborn and twelve classes from Warrior and Mage to Warlock and Necromancer. Leave them out and both are rolled at random, which is handy for filling a tavern with NPCs, handing a one-shot player a pre-made hero or seeding characters in a game you are building.

The Free plan returns the name, race, class, personality, motivation, ability scores and hit points. Paid plans add the class hit die, a background such as Criminal, and a stat summary with the total of all six scores and which ability is highest and lowest, which helps when you sort, compare or balance a party.

How it works

Ability scores are rolled the classic way: three six-sided dice for each of strength, dexterity, constitution, intelligence, wisdom and charisma, giving 3 to 18 before bonuses. The race's stat bonuses are then added to the matching scores, and a race whose bonus applies to any ability gets it on one ability picked at random. Because bonuses come after the roll, a value can go above 18. Each modifier is floor((value - 10) / 2), so 10-11 gives 0, 12-13 gives +1 and 8-9 gives -1.

hp is level-1 hit points: the maximum of the class hit die plus the constitution modifier, never below 1. A Mage with a d6 hit die and a constitution modifier of -1 has 5. class.hitDie reports the die as text, such as d6.

race and class are matched case-insensitively against the built-in lists. An unknown value returns a 400 error listing the allowed values instead of quietly substituting a random choice. When a parameter is omitted it is drawn at random with equal weight. The name joins a first and last name from lists kept per race. background, personality and motivation are each drawn independently from fixed lists, so they are not matched to the race or class.

totalStatPoints is the sum of the six final values. highestStat and lowestStat name the ability with the extreme value, checked in order from strength to charisma, so a tie goes to the earlier ability. On the Free plan class.hitDie, background, totalStatPoints, highestStat and lowestStat are null; every other field is returned on all plans.

What people use it for

Tabletop Gaming

Quickly generate NPCs or backup characters

Game Development

Create diverse character rosters for games

Creative Writing

Generate character concepts for stories

Teaching

Demonstrate character creation mechanics

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/gamecharacter

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/gamecharacter?race=elf&class=mage" \
  -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/gamecharacter

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
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

{
  "status": "ok",
  "error": null,
  "data": {
    "name": "Nimara Goldenbough",
    "race": {
      "name": "Elf",
      "traits": [
        "Graceful",
        "Keen Senses",
        "Long-lived"
      ]
    },
    "class": {
      "name": "Mage",
      "description": "Wielder of arcane magic",
      "primaryStat": "intelligence",
      "hitDie": "d6"
    },
    "background": "Criminal",
    "personality": "Ambitious and driven",
    "motivation": "Protect the innocent",
    "stats": {
      "strength": {
        "value": 13,
        "modifier": 1
      },
      "dexterity": {
        "value": 12,
        "modifier": 1
      },
      "constitution": {
        "value": 9,
        "modifier": -1
      },
      "intelligence": {
        "value": 11,
        "modifier": 0
      },
      "wisdom": {
        "value": 4,
        "modifier": -3
      },
      "charisma": {
        "value": 8,
        "modifier": -1
      }
    },
    "hp": 5,
    "totalStatPoints": 57,
    "highestStat": "strength",
    "lowestStat": "wisdom"
  }
}

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 Game Character 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 — Game Character 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