Gender API for AI agents
Gender API determines the likely gender associated with a first name, email address, or username, used for data enrichment on 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 Gender API.
Check a name's likely gender
Query gender by first name to fill in a demographic field on a contact record.
Check gender by email address
Query gender by email when a contact record only has an email on file.
Read-only enrichment lookups
Keep every gender lookup read-only, since the API only returns a probability, not a change to any record.
9 Gender API actions, graded by risk.
Every Gender API action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
9Look things up. Allowed by default.
- gender_api.get_statisticGet Gender API Statistics
- gender_api.query_by_full_nameQuery Gender by Full Name
- gender_api.query_by_first_nameGender From First Name
- gender_api.get_country_of_originGet Country of Origin
- gender_api.query_by_email_addressQuery Gender by Email Address
- gender_api.get_country_of_origin_v1Get Country of Origin (v1)
- gender_api.query_by_email_address_multipleQuery Gender by Multiple Email Addresses
- gender_api.query_gender_by_full_name_multipleQuery Gender by Full Name (Multiple)
- gender_api.query_gender_by_first_name_multipleQuery Gender by Multiple First Names
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Gender API in three steps.
- 01Your users connect Gender APIThey add their Gender API api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Gender API through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('gender_api', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Gender API connects.
Users add their Gender API 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 Gender API 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 Gender API from any agent.
Gender API and Arc0, answered.
Can I use Gender API with Claude, ChatGPT or Cursor?
Yes. Connect Gender API 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 Gender API actions you allow.
How do users connect Gender API?
Users add their Gender API 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 Gender API actions can my agent take?
9 in total: 9 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Gender API?
Yes. Allow read actions and deny writes in the Gender API policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Gender API too?
Yes. The same Gender API connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Gender API into your agent.
Your users connect Gender API once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan