GenderAPI.io for AI agents
GenderAPI.io determines the likely gender associated with a name, email address, or username through a simple lookup API, used to enrich contact and marketing records. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in GenderAPI.io.
Check a name's likely gender
Query gender by first name to fill in a demographic field on a contact record.
Check gender from a username
Get gender from a username when no real name is available on a profile.
Read-only enrichment lookups
Keep every gender lookup read-only, since the API only returns a probability, not a change to any record.
5 GenderAPI.io actions, graded by risk.
Every GenderAPI.io action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- genderapi_io.list_error_codesList Gender API Error Codes
- genderapi_io.query_by_email_addressQuery gender by email address
- genderapi_io.get_gender_from_usernameGet Gender from Username
write
2Create and change things. Allow, or ask the user first.
- genderapi_io.genderapi_get_statsGender API Get Statistics
- genderapi_io.gender_api_query_by_first_nameQuery Gender by First Name
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
GenderAPI.io in three steps.
- 01Your users connect GenderAPI.ioThey add their GenderAPI.io api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “gender API Get Statistics” can wait for the user to approve.
- 03Any agent can actYour agent calls GenderAPI.io through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('genderapi_io', { read: 'allow', write: 'ask', // genderapi_get_stats destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How GenderAPI.io connects.
Users add their GenderAPI.io api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same GenderAPI.io connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use GenderAPI.io from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
GenderAPI.io and Arc0, answered.
Can I use GenderAPI.io with Claude, ChatGPT or Cursor?
Yes. Connect GenderAPI.io to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the GenderAPI.io actions you allow.
How do users connect GenderAPI.io?
Users add their GenderAPI.io api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which GenderAPI.io actions can my agent take?
5 in total: 3 read, 2 write and 0 destructive, such as “gender API Get Statistics”. Your policies decide which of them each agent may call.
Can I make my agent read-only in GenderAPI.io?
Yes. Allow read actions and deny writes in the GenderAPI.io policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call GenderAPI.io too?
Yes. The same GenderAPI.io connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug GenderAPI.io into your agent.
Your users connect GenderAPI.io once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan