One question
May user X do Y: the whole surface, answered consistently for every service.
auth answers one question over HTTP: may user X do Y. It is authorization, not authentication: it does not log anyone in, store passwords, issue tokens or manage sessions; it trusts that the caller already knows who the user is. The model is user, role, permission: a user holds a permission exactly when a role they belong to holds it.
Who it is for. Services that need role-based access control and would otherwise build their own roles and permissions tables.
May user X do Y: the whole surface, answered consistently for every service.
Membership in a role grants its permissions; nothing else to model.
No passwords, sessions or tokens here: authentication belongs to RODMENA ID.
Plain HTTP with exact response shapes, and a Python client.
The product site has the documentation and the way in. For procurement questions, a pilot or an integration, talk to us directly.