Job titles are messy. “CHRO”, “Head of People”, and “VP HR” can mean the same seat. Arxena collapses them into a short controlled vocabulary, then uses that vocabulary for people search, org charts, and agents. The pattern is the same shape as a sector → industry hierarchy in finance — or Apollo’s short seniority list — not a public dump of every mapped title:
These cards are examples, not the full catalog. Public APIs expose flat constants (roots and grade levels), not every child node under every root.
Publish the nouns. Protect the verbs. Labels and one worked NL example are the product surface. Assignment engines, full title maps, and Boolean generators stay internal.

​
How a query works (outcomes only)

  1. You (or Claude via MCP) send a natural-language role query and a company.
  2. Arxena resolves synonyms and company-relative seniority server-side.
  3. You get people plus a small resolved / resolved_as object to sanity-check — not a walkthrough of how the match was made.
Primary path: Natural language to people at a company.

​
Public constants (ungated)

Short flat lists — enough to know what the system understands, not enough to rebuild it:
See List taxonomy constants.

​
What stays private

Authenticated classify/browse endpoints exist for integrators who already know codes. Prefer NL resolve for products and agents. Fair use: Authentication.

​
Org charts

The product org chart is a view over the same vocabulary. Query “CHRO” in the Title query bar to filter/highlight — same resolution chips, no second ontology. “Instantly queryable” means cached charts are fast; first-time companies may take a short live build (see resolved / freshness on chart payloads when present).