iblai-api-agent-sessionlisted

# iblai-api-agent-session Drive a deployed agent's **chat transport directly** and read its **sessions**. Where `/iblai-api-agent-chat` wires a hosted MCP server for conversation, this skill is the raw REST/SSE (and WebSocket) surface: POST a prompt, stream the reply, attach `metadata` that resurfaces as `client_context`, and list/inspect the resulting session records. Get `IBLAI_ORG`/`IBLAI_USERNAME`/`IBLAI_API_KEY` from `/iblai-api-login`. ## Auth & conventions - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG`, `{user}` = `$IBLAI_USERNAME`. - **Two hosts — chat is streaming/ASGI:** - Chat turn (SSE / WebSocket) → `https://asgi.data.iblai.app` - Session reads/writes → `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{user}/v1` … i.e. `…/orgs/{org}/users/{user}/sessions/…` - Not connected yet? Run **`/iblai-api-login`** first. ## Concepts **`metadata` → `client_context` passthrough.** Every chat turn (WS or SSE) may carry a `metadata` object of arbitrary key/values (`BaseConsumerPayload.metadata`). The runner folds it into the prompt the agent sees, so the agent can tailor its reply, and the consumer persists it on the session as `Session.metadata["client_context"]`. It is **session-level**: each turn's `metadata` overwrites the session's `client_context`, so it sticks across turns until you send new keys. Use it to tell one deployed agent *where/why* a message arrives (product, plan tier, page,