GenderAPI.io integration: operations for AI agents
GenderAPI.io connects to Type.com as an integration. This page lists the 8 operations documented for Claude and Codex in Type.com: 6 read, 2 write.
About GenderAPI.io
GenderAPI.io provides an API to determine the gender associated with a given name, email address, or username.
Categories: Developer Tools & IT
How to connect GenderAPI.io to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
8 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
- Read
Get Capabilities
GET /api/v2
- Read
Get Error Catalog
GET /api/v2/errors
- Read
Get Open Api
GET /api/v2/openapi.json
- Read
Get Usage
GET /api/v2/usage
- Read
Predict Gender Get
Browser-friendly single prediction. Same pricing and validation as POST. Every request is processed and billed separately, including repeated requests. Responses are not cacheable. HEAD is rejected.
- Read
Validate Phone
country is required unless number starts with +. This checks number structure, not subscriber existence.
- Write
Predict Gender
Single name, email or username. Ordinary aimode defaults to fallback and costs 1 credit even after AI fallback. forceToGenderize true always checks the dataset first: a resolved gender costs 1; otherwise nickname-based AI costs 2 total, including a valid null result.
- Write
Predict Gender Batch
Maximum 50 items (10 for IP trials). Each item supports name/email/username with independent country and AI options. Defaults to off; ordinary fallback costs 1, always costs 2, force costs 1 for dataset or 2 for AI. Planning failure rejects the whole batch before debit.
No operations match.
See How connections work for access and permissions, or browse all integrations.