iblai-api-agent-memorylisted

# iblai-api-agent-memory Manage an agent's memories through the API: browse and filter what an agent has remembered, curate global (cross-agent) memories, add / edit / delete individual memories, manage the categories memories are filed under, and control capture / recall settings. Use when inspecting or curating what an agent remembers. ## 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 / two spellings:** endpoints live under the `ai-mentor` base `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}` (the leading `…` below). A twin `ai-agent` base mirrors every route with the `mentor` path token swapped for `agent` (`…/mentors/{mentor}/mentor-memories/` ↔ `…/agents/{agent}/agent-memories/`); either works. - **Two path bases:** user-scoped routes hang off `…/orgs/{org}/users/{username}` (written `{u}` below); memory **categories** hang off `…/orgs/{org}/mentors/{mentor}` directly (no user segment). - Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`, `IBLAI_USERNAME`, and `IBLAI_API_KEY`. ## Concepts Two PGVector-backed memory stores ("memsearch") sit behind these endpoints: - **Global memories** (`UserGlobalMemory`) — scoped to a user + org, shared across every agent; facts any agen