iblai-api-agent-accesslisted

# iblai-api-agent-access Manage role-based access control that decides who can **edit**, **chat with**, or **view analytics for** an agent. Searches resolve users and groups; every grant and revoke flows through the single `mentor-access/` write endpoint. Use when controlling who can edit, chat with, or view analytics for an agent. ## Auth & conventions - **Base URL:** `https://api.iblai.app` - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG`, `{username}` = `$IBLAI_USERNAME`, `{mentor}` = the agent's unique id (e.g. `d17dc729-60fd-4363-81a0-f67d9318b03e`). - **Access writes** go through one endpoint — **POST** `https://api.iblai.app/dm/api/core/rbac/mentor-access/` — keyed by the numeric `mentor_id`, adding/removing users, groups, and emails per `role`. - Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`, `IBLAI_USERNAME`, and `IBLAI_API_KEY`. ## Reads - **GET** `…/users/{username}/mentors/{mentor}/settings/` — resolve the numeric `mentor_id`. - **GET** `https://api.iblai.app/dm/api/core/rbac/mentor-access/?mentor_id={id}&platform_key={org}` — list current role policies. - **POST** `https://api.iblai.app/dm/api/core/rbac/permissions/check/` — can the user search users/groups? ```json { "platform_key": "string (required)", "resources": ["/users/", "/groups/"] } ``` - **GET** `https://api.iblai.app/dm/api/core/platform/users/?platform_key={org}&platform_org={or