{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/hr.directory-lookup/",
    "json": "https://www.anchorterminal.com/niches/hr.directory-lookup/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/hr.directory-lookup/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/hr.directory-lookup/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 7 | 12 | 24 | 4 |\n\n## What counts as done\n\nName, title, department, manager and work contact for each match from one search call, with no field returned that the user's own HR permissions hide (pay, personal address, ID numbers).\n\nHow agents ask for it: who is Priya's manager; who's in the design team; find the person who runs payroll; what's Sam's job title\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Rippling (People Center, Inc. dba Rippling)**: The MCP runs as the connected employee, with search_people among its tools and no SSNs, home addresses or tax IDs exposed; REST tokens see the intersection of the owner's permissions, with hidden fields listed in __meta.redacted_fields. Workers carry role, manager and department.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **BambooHR (Bamboo HR LLC)**: GET /api/v1/employees takes filter, fields and cursor paging, so name, title, department, supervisor and work email come in one call, and the MCP enforces the user's own permissions. Restricted fields drop silently, and acc-01 got every column but the id back null.\n- **Deel (Deel, Inc.)**: GET /people takes search, teams and fields with offset paging, so matching people come back in one call, and the MCP runs on the user's OAuth consent. Whether an organisation token hides fields the user's role can't see is not documented.\n- **Factorial (Everyday Software, S.L.)**: Reads all Employees returns a payload restricted to the caller's permission group, and a User Token works as one employee. The list filters by ids, not by name or team, and team membership comes from a separate endpoint, so one search call is not enough.\n- **HiBob (Hi Bob Ltd.)**: POST /people/search returns chosen fields for many employees in one call, with field-level permissions applied. Calls run as an API service user, not the employee, so the token sees what its permission group allows, and unpermitted fields drop from a 200 with no warning.\n- **Humaans (Humaans Software UK Ltd)**: GET /api/people pages with $limit and $skip, and a public:read token sees only company-public profile data while private:read adds banking and leave reasons, so scope caps what leaks. No name or team search parameter on people was found, and manager lines come through org units and reportingTo.\n- **Remote (Remote Europe Holding B.V.)**: GET /v1/employments filters by name, email and status with paging, but job title and manager come from separate endpoints (employment job, company structure nodes), so one search call doesn't return all fields. Customer API tokens carry chosen scopes, not the user's own HR permissions.\n- **Zoho People (Zoho Corporation Private Limited)**: Search Records Based on Record Values queries the employee form by a field value, up to 200 records a call, returning the form's columns. OAuth tokens act as the authorising user, but the pages read don't say whether fields hidden by the user's role are withheld.\n\n## What stops agents finishing\n\n- token sees fields the user cannot (or none at all, acc-01)\n- directory search not exposed, only full employee lists\n\n## Around it\n\nBefore: chat.user-question. After: productivity.post-message, scheduling.find-time.\n\n## Where this comes from\n\nWeight 24 of 100 in HR \u0026 employee operations: 4 of 13 accounts (AI memory and assistant connectors for BambooHR and Rippling, a scoped directory plugin, a custom report returning nulls); counts are low, weight set by hand as the commonest agent request in vendor MCP docs\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/hr.directory-lookup.json, or the MCP tool get_use_case with id hr.directory-lookup. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Answer who someone is and where they sit",
        "url": ""
      }
    ],
    "description": "Answer who someone is and where they sit: 1 companies fully do it, 7 with a limit, 12 carry the tag. Every listing in HR \u0026 employee operations with the reason and a source.",
    "facts": null,
    "h1": "Answer who someone is and where they sit",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/hr.directory-lookup/",
    "published": "",
    "section": "agents",
    "title": "Answer who someone is and where they sit | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/hr.directory-lookup/"
  },
  "tokens": {
    "markdown": 1200,
    "slim": 280
  },
  "version": 1
}
