Iblai api ecosystem

iblai-api-ecosystem

Orientation to the ibl.ai open-source family. Everything ibl.ai ships is built on one hosted backend — https://api.iblai.app — with each organization (org) fully isolated (its own users, agents, branding, data). The repos differ only in what they let you do to that backend: operate it, build on it, fork a finished product, or host it yourself.

You are already inside iblai/api — the repo whose skills you're reading. This skill exists so you know where the sibling repos and tooling fit, and which one to reach for next. It has no endpoints; the detail lives in the reference files below.

The five-repo family

Repo	What it is	Reach for it when
iblai/api (this repo)	Management layer — skills that map to exact api.iblai.app REST endpoints, plus one hosted chat MCP server. Operate the platform headlessly from an agent, terminal, or CI — no UI.	You want to configure agents, datasets, memory, users, roles, notifications, discovery, profiles, or analytics as / commands. Install: npx skills add iblai/api, then run /iblai-api-login.
iblai/vibe	Build layer — Next.js SDK, pre-built components, Claude Code skills, and a scaffolding CLI for creating new apps on the backend. Auth is client-side SSO (no API tokens to manage).	You're building a brand-new app on the ibl.ai backend. Install: npx skills add iblai/vibe. See references/app-tooling.md.
iblai/os	Sample app — the open-source AI agent platform running at os.ibl.ai. A complete, production-grade codebase (web + native desktop/mobile), built with vibe.	You want a full AI-agent product to fork, point at your org, rebrand, and ship. See references/repos.md.
iblai/lms	Sample app — the open-source skills-intelligence platform at lms.ibl.ai: courses, competencies, credentials, analytics. Also built with vibe.	You want a learning/upskilling product to fork and ship. See references/repos.md.
iblai/iblai-infra-cli	Deploy layer — provision the backend on your own AWS account or servers with Terraform + Ansible (given access to the backend images).	You need to self-host instead of running against hosted api.iblai.app. See /iblai-api-infrastructure for the details.

How they relate: vibe builds apps like os and lms on the same backend that api operates and iblai-infra-cli deploys. The two sample apps prove what the stack produces; you can clone either and modify it. A free tier is available on the hosted backend; for a license to the full platform codebase (to run locally or self-host), contact ibl.ai/contact.

Which do I reach for?

• Operate an existing org (agents, users, analytics, no UI) → this repo. Start with /iblai-api-login; hold a live conversation with a deployed agent via /iblai-api-agent-chat (the one runtime capability that isn't REST).
• Build a new app on the backend → iblai/vibe + the iblai-app-cli scaffolder → references/app-tooling.md.
• Fork a finished product → iblai/os (agents) or iblai/lms (learning) → references/repos.md.
• Self-host the backend → iblai/iblai-infra-cli → /iblai-api-infrastructure.

Reference material

Full, deduped detail from the developer docs (which are being retired) lives here:

• references/repos.md — per-repo deep dive: what each of api / vibe / os / lms / iblai-infra-cli is, who it's for, its features, tech stack, deploy options, and quick start. Reach here to decide which repo to fork or study.
• references/app-tooling.md — the vibe build layer in depth: the iblai-app-cli scaffolder, the @iblai SDK/API/MCP packages, the full vibe skills catalog, the shared backend's capabilities, and the end-to-end quickstart (scaffold → connect → customize → deploy web/desktop/mobile).

Related skills in this repo: /iblai-api-login (connect an org — run first), /iblai-api-agent-chat (runtime chat MCP), /iblai-api-infrastructure (self-hosting with iblai-infra-cli).