GenderAPI.io
for LuumenAI
Resolve the gender behind a name, email, or username, read-only.
Ask GenderAPI.io what gender is associated with a first name, an email address, or a username, and get the answer back in the terminal. Check remaining account usage with GENDERAPI_IO_GENDERAPI_GET_STATS, and look up what a failed response meant with GENDERAPI_IO_LIST_ERROR_CODES. Connects with an API key. All five tools are read-only.
The GenderAPI.io toolbox
5 tools, all read-only. They answer instantly, and every call is logged.
- ReadGender API Get StatisticsRetrieve account usage statistics from GenderAPI.io.
- ReadQuery Gender by First NameDetermine gender by querying first name.
- ReadGet Gender from UsernameDetermine gender from a username or nickname.
- ReadList Gender API Error CodesList all possible error codes returned by Gender API.
- ReadQuery gender by email addressDetermine gender from an email address.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 5 tools LuumenAI has for GenderAPI.io is read-only, so it can answer questions from GenderAPI.io but cannot change anything in it. Read actions still follow the configured access and approval policy, and are recorded on the audit trail.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to GenderAPI.io is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put GenderAPI.io to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.