NamSor
for LuumenAI
Read name classifications and account usage from NamSor in your terminal
Ask about a name and get an answer back in the terminal. NAMSOR_PARSE_NAMES splits full names into first and last parts. NAMSOR_CLASSIFY_GENDER, NAMSOR_CLASSIFY_ORIGIN, NAMSOR_CLASSIFY_RESIDENCE_COUNTRY, and NAMSOR_CLASSIFY_DIASPORA infer likely attributes, and NAMSOR_CLASSIFY_PROPER_NOUN_TYPE sorts personal names from brands and places. NAMSOR_GET_ACCOUNT_USAGE reports plan, quota, and overage without exposing the API key. All seven tools are read-only, so they answer immediately.
The NamSor toolbox
7 tools, all read-only. They answer instantly, and every call is logged.
- ReadClassify Name DiasporaInfer likely diaspora or ethnicity labels for one or more names within a known country of residence.
- ReadClassify Name GenderInfer likely gender for one or more first-and-last names.
- ReadClassify Name OriginInfer likely countries and region of origin for one or more first-and-last names.
- ReadClassify Proper-Noun TypeClassify one or more proper nouns as likely personal names, brand names, place names, or other NamSor types.
- ReadClassify Residence CountryInfer likely countries and region of residence for one or more full personal names.
- ReadGet Account UsageReturn the connected NamSor account's plan, quota, current billing-period usage, limits, and overage summary without exposing its API key.
- ReadParse Personal NamesParse one or more full personal names into likely first-name and last-name components.
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 7 tools LuumenAI has for NamSor is read-only, so it can answer questions from NamSor but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to NamSor 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
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut NamSor to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.