Getting started — the whole journey

Mirrored from iblai/vibe · docs/getting-started.md. This page is generated — edit it in the repository, not here.

The README gives you the three steps. This page is what actually happens in each, which entry point is yours, and what to do when you are not starting from scratch.

Which entry point is yours

How sign-in and organizations really work: auth-model.md. The data every app is built on: domain-model.md.

The journey

0. Get an organization — sign up at ibl.ai/join; it creates your account and your organization. (Everyone is also in the shared main org — that one is not yours.) → Platform lifecycle
1. Get two values — your org key (on login.iblai.app/me) and a Platform API Token (os.ibl.ai → Admin → Integrations → APIs → Add API). → same doc
2. Scaffold and run — install the skills, run /iblai-vibe-ops-init, pnpm dev, sign in, pick or create your agent on /setup.
3. Add the core — profile, admin area, custom user and org data, memory, analytics, notifications: one skill each, below.
4. Make it yours — your pages with shadcn/ui; anything without a component through the REST API (/iblai-vibe-api).
5. Charge (optional) — /iblai-vibe-pricing: how you are billed, and the three ways to bill your users.
6. Ship — /iblai-vibe-ops-deploy for a URL; /iblai-vibe-ops-build and /iblai-vibe-ops-release for desktop, mobile, and the stores.

Every step in detail, with what to click and what to check: platform-lifecycle.md.

Connecting your organization

/iblai-vibe-connect opens login.iblai.app/connect: you sign in (or create an organization), pick the organization, click Connect, and the agent receives the org key, your username, and a fresh Platform API Token on a loopback callback — it writes iblai.env, .env, and .env.local and never shows the token. No browser (SSH, a container)? The same page has a manual mode you paste into the chat. Until the hosted page ships, the skills fall back to asking for the two values and telling you exactly where they are: connect-flow.md.

The core app

What /iblai-vibe-ops-init gives you, and the skill that owns each piece. ★ marks the six core data families almost every app reads or writes (which scope stores what) — each links its headless twin, the iblai-api-* skill that documents the same data over REST.

How money works

• You run on prepaid, rechargeable credits with a hard ceiling (plans Free → Trial → Premium, opt-in auto-recharge, no per-seat fees). Add your own LLM keys for more models; put spend caps on the org, an agent, or one user on one agent.
• Your users can be charged three ways: pay-to-enter for the whole app on your own Stripe key with no commission (/iblai-vibe-monetization-app-paywall, the vibe-agent model); per-item sales with subscriptions and revenue dashboards via Stripe Connect (/iblai-vibe-monetization → onboard, configure, checkout, subscription, analytics); or reselling platform credits (/iblai-vibe-credit, /iblai-vibe-billing, /iblai-vibe-agent-billing).
• One page decides: /iblai-vibe-pricing.

Two families of skills, one install

Every skill carries a kind in its frontmatter (ui, api, guide, ops, security — docs/skill-kinds.md). The name prefix tells you the family; the kind tells you whether there is a screen.

Builders use both: the ui skill mounts the component, its Platform data table names the api twin for anything the component doesn't cover, and /iblai-vibe-api is the server-route pattern that joins them. The iblai-api-* family is the former iblai/api repository, merged here with its authoring contract intact — docs/api-skills.md.

Headless API skills (kind: api)

Connect once with /iblai-api-login (org key, username, Platform API Token → .env + iblai.env), then any skill below is a / command that calls https://api.iblai.app with Authorization: Api-Token.

Every name above is /iblai-api-<name>.

The full, tiered catalogue with one-line descriptions is in CLAUDE.md. Skills are in skills/; npx skills add installs them into your project's .claude/skills/. Read them, extend them, or write your own — the front door for agents is /iblai-vibe.

The ibl.ai backend

https://api.iblai.app powers every vibe app; you build, host, and maintain no backend services. It provides SSO (OAuth/OIDC/SAML) with multi-org isolation and RBAC; agents with streaming, tools, RAG, memory, voice, and any LLM; analytics; notifications; per-user and per-org metadata; credits, spend caps, and Stripe billing. In the browser the SDK sends the signed-in user's session token; your server holds one org-scoped Platform API Token in the gitignored iblai.env / .env.local. How that fits together: docs/security-model.md.

Two MCP servers

@iblai/mcp — SDK documentation for your coding assistant (components, hooks, RTK Query endpoints, provider setup). .mcp.json at the project root (vibe-starter ships it):

{
  "mcpServers": {
    "iblai": { "command": "pnpm", "args": ["dlx", "@iblai/mcp"] }
  }
}

(npx -y @iblai/mcp in npm projects.) It gives your assistant get_component_info, get_hook_info, get_api_query_info, get_provider_setup, create_page_template, get_playwright_helper_info.

iblai-agent-chat — a hosted MCP server for the one runtime capability that is not a REST call: holding a live conversation with a deployed agent (streamed responses, tool use, RAG). No install; wire it with /iblai-api-agent-chat or by hand from mcp/iblai-agent-chat/README.md:

claude mcp add iblai-agent-chat --transport http https://asgi.data.iblai.app/mcp/agent-chat/ \
  --header "Authorization: Api-Token YOUR_API_TOKEN" --header "X-Mentor-Unique-Id: YOUR_AGENT_UUID"