iblai-api-agent-supportlisted

# iblai-api-agent-support Manage an agent's human-support tickets through the API: list and filter the tickets users raised with an agent, read a ticket's reply thread, respond as the support team, move tickets through their lifecycle, and close or delete them. Use when triaging or responding to support requests escalated from agent chats. ## 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`). - **Prefix:** every route below hangs off `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{username}` (written `{u}` below). The path token is named `user_id` on the wire but takes the **username**. - Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`, `IBLAI_USERNAME`, and `IBLAI_API_KEY`. - DELETE calls are destructive — confirm with the user first. ## Concepts - **Tickets are opened by the agent, not by this API.** When a user asks an agent for human help mid-chat, the agent's human-support tool files a `HumanSupportTicket` — there is **no POST create endpoint** here. The requester fields (`username`, `email`, `full_name`, `user`) and the source `session` are resolved server-side from that chat; `subject` and `description` are authored by the agent (the `description` is often HTML or Markdown,