Anthropic Seat Inventory
Overview
An MSP that supplies or manages Claude for a client needs to answer three questions on a schedule: how many seats are in use, who holds the powerful roles, and whether people who left still have access. This skill answers them from the Admin API. It reads only; removing a user or revoking an invite is done by a client admin in Claude Console.
Anti-triggers
- API keys a leaver created — keys outlive their creator's seat; use key-and-audit-review (admin-gated).
- Who is actually using Claude Code — membership is not usage; use claude-code-adoption.
Key Concepts
- Organization role (
roleon a user). Console and API orgs useuser,developer,billing,admin, andclaude_code_user. Claude Enterprise orgs useuser,owner,primary_owner,membership_admin, andmanaged. Filter with therolesargument. - Invites have a status of
pending,accepted, orexpired. A pending invite is a seat about to be taken; an old pending invite to a departed person is still a way in once accepted. - Workspaces split keys, usage, and limits. A user can belong to the
org but to only some workspaces, each with its own workspace role. The
default workspace is hidden unless you pass
include_default: true; archived workspaces needinclude_archived: true.
Workflows
Seat count
anthropic_admin_organization_get- confirm the org.anthropic_admin_users_listwithlimit: 1000, pagingafter_iduntilhas_moreis false.- Group by
roleand count. Report the total, the count per role, and the newestadded_atdates (recent additions explain a jump since the last review). anthropic_admin_invites_listwithstatuses: ["pending"]- pending seats, listed separately from active ones.
Admin-role review
anthropic_admin_users_listwithroles: ["admin"](Console org) orroles: ["owner", "primary_owner", "membership_admin"](Enterprise).- Compare against the people the client says should administer the org. Flag anyone extra, and flag personal email domains on admin seats.
- For workspace-level admin,
anthropic_admin_workspaces_list, thenanthropic_admin_workspace_members_listper workspace, and look at the workspace role on each membership.
Offboarding check
Given a leaver's email address:
anthropic_admin_users_listwithemail- still a member?anthropic_admin_invites_listwithemail- any invite still pending?- If a user ID came back,
anthropic_admin_workspace_member_getfor each workspace, or note the org membership alone if they have no workspaces. - Report "still has access: yes/no" with the evidence, and hand the removal to the client admin. If the caller has the admin tier, continue with the leaver's API keys in key-and-audit-review.
A person missing from anthropic_admin_users_list has no Console seat in
this org, but may still be a member of a different Anthropic org the
client owns. Say which org you checked.
Gotchas
anthropic_admin_users_listfilters by exact email. Aliases and plus addresses do not match; when the client's identity provider uses aliases, list everyone and match yourself.- Counting seats from one page undercounts silently. Page to the end.
- Workspace membership is per workspace. There is no single call for "all workspaces this user is in"; loop the workspaces.
- Invite and user records hold names and email addresses. Keep reports that leave the MSP to counts and roles unless the client asked for names.
Related Skills
- api-patterns - pagination, tiers, errors
- key-and-audit-review - keys a member created, and role-change history