Name Demographics API: Enrich Profiles With Age, Gender, and Nationality Estimates

Signup forms often ask for information that users may prefer not to provide directly. Age range, gender, and nationality can be useful for personalization, analytics, fraud detection, and audience research—but adding more required fields can also increase friction and reduce completion rates.

The Name Intelligence API provides a lightweight alternative: estimate demographic attributes from a person’s name after signup. With a single request, you can enrich a profile with likely age, gender, and nationality data while keeping the form short and user-controlled.

What the Name Intelligence API returns

The API analyzes a submitted name and returns estimates with confidence-related metadata. Results are probabilistic, not verified identity data. Treat them as signals for segmentation or personalization—not as facts about an individual.

A typical request looks like this:

curl -X GET "https://api.theglitch.store/v1/name-intelligence?name=Maria%20Garcia" \\
  -H "Authorization: Bearer YOUR_API_KEY"

Example response:

{
  "name": "Maria Garcia",
  "age": {
    "estimate": 34,
    "range": "25-44",
    "confidence": 0.72
  },
  "gender": {
    "estimate": "female",
    "confidence": 0.96
  },
  "nationality": [
    {
      "country": "ES",
      "probability": 0.41
    },
    {
      "country": "MX",
      "probability": 0.22
    },
    {
      "country": "AR",
      "probability": 0.09
    }
  ],
  "credits_used": 1
}

The response includes an age estimate and range, a likely gender classification, and a ranked list of possible nationalities. Nationality estimates are especially useful when a name is common across multiple countries, because the ranked probabilities make uncertainty visible.

Enrich a signup flow after submission

A practical integration pattern is to create the account first, then enrich the profile asynchronously. This keeps the signup experience fast and avoids blocking registration if the enrichment request fails.

async function enrichProfile(name, userId) {
  const params = new URLSearchParams({ name });

  const response = await fetch(
    `https://api.theglitch.store/v1/name-intelligence?${params}`,
    {
      headers: {
        Authorization: `Bearer ${process.env.GLITCH_STORE_API_KEY}`
      }
    }
  );

  if (!response.ok) {
    throw new Error(`Name Intelligence request failed: ${response.status}`);
  }

  const estimate = await response.json();

  await saveProfileAttributes(userId, {
    estimatedAge: estimate.age?.estimate ?? null,
    estimatedAgeRange: estimate.age?.range ?? null,
    estimatedGender: estimate.gender?.estimate ?? null,
    nationalityEstimates: estimate.nationality ?? [],
    demographicSource: "name-intelligence",
    demographicConfidence: estimate.gender?.confidence ?? null
  });
}

Keep the API key on your server. Do not call the service directly from browser code or expose the key in a mobile application. Your backend should also validate the name field, URL-encode user input, handle timeouts, and avoid retrying requests indefinitely.

For Python applications, the same workflow can be implemented with requests:

import os
import requests


def get_name_estimate(name: str) -> dict:
    response = requests.get(
        "https://api.theglitch.store/v1/name-intelligence",
        params={"name": name},
        headers={"Authorization": f"Bearer {os.environ['GLITCH_STORE_API_KEY']}"},
        timeout=5,
    )
    response.raise_for_status()
    return response.json()


estimate = get_name_estimate("Kenji Sato")
print(estimate.get("age", {}).get("range"))

Use estimates responsibly

Names can be ambiguous, culturally diverse, transliterated, shared by people of different backgrounds, or intentionally abbreviated. A name-based estimate may be inaccurate for any individual. Avoid using these results as the sole basis for eligibility, pricing, employment, credit, housing, healthcare, or other high-impact decisions.

When displaying personalized content, provide neutral defaults and let users correct or override estimates. Store the source and confidence values alongside the attributes so downstream systems can distinguish inferred data from information supplied by the user. You should also document the purpose of enrichment, limit retention, and follow applicable privacy and data-protection requirements.

Pricing

Name Intelligence API usage is priced at $0.01 per credit. There is no subscription requirement. Each successful lookup uses one credit, making it suitable for occasional enrichment, batch experiments, and pay-as-you-grow production integrations. Before sending large volumes, consider caching results where appropriate and monitor credit usage from your application.

With a server-side request, explicit uncertainty handling, and user-friendly fallbacks, the Name Intelligence API can add useful demographic context without turning your signup form into a questionnaire.