iblai-api-profile-metadatalisted

# iblai-api-profile-metadata Read and write per-user, per-organization metadata via the API: a key-value store for preferences, app settings, feature flags, and onboarding progress, all served from a single `…/dm/api/core/users/platform-metadata/` endpoint. Defaults to the signed-in user; admins can target another user. ## Auth & conventions - **Base URL:** `https://api.iblai.app` - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG` (passed as the `platform_key` query param), `{username}` = `$IBLAI_USERNAME`. - **Host:** all operations hit `…/dm/api/core/users/platform-metadata/` and take `?platform_key={org}`. - Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`, `IBLAI_USERNAME`, and `IBLAI_API_KEY`. ## Concepts - **One object per user × org.** Metadata is a single JSON object stored per (`{username}`, `{org}`) pair, so the same user holds independent metadata in each org. Keys are arbitrary strings; values are arbitrary JSON (strings, numbers, booleans, nested objects/arrays). The store enforces no schema, key namespace, or value types — any namespacing convention is yours to keep, not the API's. - **Auto-created on first use.** GET/PATCH/PUT create the record on demand; a GET for a user with no metadata yet returns `"metadata": {}` (`200`, never `404`). - **Admin cross-user access.** Add `&username={other}` to act on another user. The caller must be an **org admin*