Skip to main content

agentrouter.identity.v1.IdentityService

IdentityService carries the admin-side endpoints that the auth middleware and onboarding paths need. ResolveApiKey (milestones A+B), the GetUser/ListUsers directory lookups and the BanUser/UnbanUser moderation pair are landed; the rest of the admin surface ships in milestone C.

Every RPC here names its subject in the request. That is the line against MeService: an RPC that acts on ANOTHER user belongs on this service even when only a session may call it (BanUser/UnbanUser). Doc visibility is per-RPC: ResolveApiKey stays out of the customer reference via its "internal" scope, while the GetUser/ListUsers directory lookups are customer-facing (users_reader scope, which admin satisfies through implication; accept API_KEY).