Integration

GenderAPI.io integration

GenderAPI.io estimates the likely gender behind a first or full name, an email address or a username, optionally scoped to a country, with a confidence score and the number of dataset samples behind it. It can process up to 50 mixed lookups in one batch, validate and format a phone number into E.164, and report the remaining credit balance. Every completed prediction is billed in credits (1 for a dataset lookup or automatic AI fallback, 2 when AI is forced), including predictions that come back unknown, and a phone validation costs 1 credit. The capabilities, error catalog and OpenAPI document routes, and the browser GET variant of the prediction, are not exposed. Authentication is the account API key sent as a Bearer token in the Authorization header; a request without a recognised key falls back to a shared IP trial of 10 credits per day.

Connect GenderAPI.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in GenderAPI.io.Built from the 4 GenderAPI.io tools below, on the connection you add once.

What you can do with GenderAPI.io

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Gender, 2 operations

predict_genderPredict genderPOSTPredict the likely gender (male, female or null) behind one name, email address or username, with confidence. Costs 1 credit (2 with ai_mode always), billed even when the result is unknown.
predict_gender_batchPredict gender batchPOSTPredict genders for up to 50 names, emails and usernames in one call (10 on the IP trial). Each result in data carries its index, your id and charged_credits; check each item for an error.

Phone number, 1 operation

validate_phoneValidate phonePOSTCheck that a phone number is structurally valid for its country and format it in E.164. Does not check that the line exists. Costs 1 credit, even when valid is false.

Usage, 1 operation

get_usageGet usageGETRead the account's remaining credit balance (shared between API v1 and v2). Free. Without a recognised key it reports the IP trial allowance and its reset time.

Use GenderAPI.io from Claude Code, Cursor or Codex

Connect GenderAPI.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its GenderAPI.io operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect GenderAPI.io

Create your workspace
Sign up free. Nothing to install.
Connect GenderAPI.io once
Add your GenderAPI.io connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.