iblai-api-external-service-proxylisted

# iblai-api-external-service-proxy A service-agnostic **gateway** for calling third-party AI providers (ElevenLabs, HeyGen, …) *through* ibl.ai instead of hitting them directly. One request shape fronts every provider; the provider's API key is stored server-side per org and injected upstream, so the client never holds it. Work in two phases: **discover** a service's endpoints, then **invoke** one. Configure the provider keys with `/iblai-api-integration`; get `IBLAI_ORG`/`IBLAI_API_KEY` from `/iblai-api-login`. ## Auth & conventions - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. The token must belong to a **platform admin** — all three endpoints are platform-admin gated (a non-admin token → `403`; no token → `401`). - **Base:** `https://api.iblai.app/dm/api/ai-proxy/orgs/{org}` — `{org}` = `$IBLAI_ORG` (a.k.a. `platform_key`). App segment is `ai-proxy`; backend routes are bare `/api/...`, the gateway prepends `/dm`. - Run `/iblai-api-login` first to populate `$IBLAI_ORG` / `$IBLAI_API_KEY`. - Provider **credentials are configured out-of-band** by a platform admin (see Notes), not through this API. Resolution follows each service's `credential_policy`. - **Confirm with the user first** for any billable or destructive action — invoking a `tts`, `generate-*`, `translate-*`, dubbing, or delete action hits a paid third-party API or removes provider-side data. ## Concepts Everything here is read off **service discovery** (below) — th