Give your agents a reliable answer to “who should act?”
Build agents that can resolve the right approver, owner, reviewer, group, role, or delegated contact without embedding organizational logic in prompts or application code.
Roster gives agents one participant-resolution surface across MCP and REST — backed by projects, directory data, participant metadata, memberships, and active delegations.
One tool call away from the right participant
Instead of embedding approver tables and group aliases in prompts, your agent asks Roster in plain language and receives an authorized, request-relevant participant.
One governed tool for organizational routing
Use resolve() for open-ended responsibility questions. Reach for the exact tools when the agent needs to inspect specific resources. Every capability is authorized against the acting identity, credential scopes, project access, and resource rules.
Ask an open-ended question and receive an authorized, request-relevant participant — with metadata explaining why.
Inspect the projects, participants, participant members, and labels the agent is authorized to see.
Check active delegations and coverage so the agent routes to the right person during absences.
Look up materialized users, groups, and memberships that back a participant selection.
Review previous resolutions attributed to the agent’s identity for debugging and audit.
Every capability is available through the MCP server and the REST API, using the same authorization model.
Build with the surface your agent already uses
Same authorization model, same tools, same participant model — reached through the interface that fits your framework.
What Roster evaluates on every resolve
Every resolve request is answered against the acting identity’s authorized view — never the raw directory.
Chooses the next action, when to pause for human review, and how the workflow continues. It doesn’t know who should approve, own, or receive the escalation.
Returns the current person, group, role, owner, approver, or delegate from live organizational context — with the metadata to explain the choice.
Built for production agent access
Ship agents with the same rigor you’d expect from any privileged service — dedicated identities, scoped tools, and auditable resolution.