Genderize plugin

• A key is optional. A live probe without one still answered, because Genderize serves a small IP-scoped allowance (10 names per window in a probe on 2026-11-14) before it asks for an account. Passing a key raises the allowance and is what the account is billed against, so configure one for anything beyond a trial. Because a missing key is valid, Corsair does not prompt a tenant for one: connect the key with a connect link or pass key to genderize(). On a shared server every keyless tenant draws on the same IP allowance.
• A name it does not know is not an error. The answer is HTTP 200 with gender: null, probability: 0 and count: 0. The name still counts against the monthly quota, so check gender rather than relying on the call to fail.
• A full name is more accurate than a first name. Every part carries signal: a surname such as Jónsdóttir is used only by women, so Alex Jónsdóttir resolves as female even though Alex alone leans male. Genderize finds the name parts itself, so Tanaka Hiroshi and Hiroshi Tanaka give the same answer.
• Country changes the answer. Kim is mostly female worldwide but overwhelmingly male in Denmark, so pass country_id when the country is known.
• A batch counts each name against the monthly quota. batch sends up to 100 names in one request and answers an array in the same order as the input. Its country_id applies to every name in it, not to one.
• 429 means two different things. It is either the exhausted quota (Request limit reached), which the plugin does not retry because it lasts until the window resets, or a short-term throttle (Request too low to process), which it retries with backoff.

• 2 typed API operations

Setup

npm install corsair @corsair-dev/genderize better-sqlite3
npm install --save-dev @types/better-sqlite3

yarn add corsair @corsair-dev/genderize better-sqlite3
yarn add --dev @types/better-sqlite3

pnpm install corsair @corsair-dev/genderize better-sqlite3
pnpm install --save-dev @types/better-sqlite3

bun add corsair @corsair-dev/genderize better-sqlite3
bun add --dev @types/better-sqlite3

import Database from 'better-sqlite3';
import { createCorsair } from 'corsair';
import { genderize } from '@corsair-dev/genderize';

export const corsair = createCorsair({
	plugins: [
		genderize(),
	],
	database: new Database('corsair.db'),
	kek: process.env.CORSAIR_KEK!,
	multiTenancy: true,
	hub: {
		projectApiKey: process.env.CORSAIR_API_KEY!,
		signingSecret: process.env.CORSAIR_SIGNING_SECRET!,
	},
});

genderize()

const { connectUrl } = await corsair.manage.connect.createLink({
	plugin: 'genderize',
	tenantId: 'acme',
});
// redirect the user's browser to connectUrl

Example API calls

const tenant = corsair.withTenant('acme');
await tenant.genderize.api.name.predict({ name: 'peter' });

What’s next