📅 Book a 30-min Demo📞 Call/text (571) 293-0242

Last updated

API (`iblai/api`)

GitHub: github.com/iblai/api — Operate any ibl.ai organization from your AI agent. Skills + a chat MCP server. 33 skills · MIT license · works with Claude Code, Cursor, GitHub Copilot, and 15+ other skills-compatible agents.

Overview

iblai/api is a toolkit for operating the ibl.ai platform headlessly — from a coding agent, a terminal, CI, or any MCP-capable assistant, with no UI required. It packages every agent-configuration and platform-admin operation as a skill that maps directly to its exact REST endpoints on api.iblai.app (method, URL, body), plus a hosted MCP server for the one runtime capability that isn't a REST call: chatting with a deployed agent.

In the five-repo family, this is the management layer: iblai/vibe teaches your agent to build new apps on the ibl.ai backend, iblai/os and iblai/lms are complete sample applications on that backend, and iblai/iblai-infra-cli deploys the backend on your own infrastructure — while iblai/api lets an AI agent run the platform itself via the REST API.

It is for developers and platform administrators who want to configure agents, manage datasets and memory, administer users and roles, send notifications, and pull analytics as / commands instead of docs hunts. The skills run against the hosted api.iblai.app environment; for a license to the full platform codebase to run locally or self-host, contact ibl.ai/contact.

How It Works

  1. Install — npx skills add iblai/api drops the skills into your project.
  2. Connect — run /iblai-login to capture your org + username from login.iblai.app/me and store an Api-Token in .env.
  3. Operate — invoke any /iblai-* skill; it fills in your org, username, and (where relevant) the agent id, then calls api.iblai.app.
  4. Automate — chain skills, or connect the hosted chat MCP server to your assistant to talk to agents at runtime.

Every skill is endpoint-accurate: it carries the real api.iblai.app request shapes, so your agent calls the platform correctly the first time. Authenticate once and you can target any organization you belong to by org key + Api-Token.

Skills

After installing, use these directly in your AI agent as / commands. One skill per operation — each /iblai-* skill maps one capability.

Setup
/iblai-login

Connects an organization — opens login.iblai.app/me, captures org + username + Api-Token into .env. Run this first.

Agent skills

Everything about a single agent — creation, identity, model, prompts, knowledge, safety, and operations:

/iblai-agent-create        /iblai-agent-datasets
/iblai-agent-settings      /iblai-agent-embed
/iblai-agent-sandbox       /iblai-agent-memory
/iblai-agent-access        /iblai-agent-history
/iblai-agent-llm           /iblai-agent-audit
/iblai-agent-prompts       /iblai-agent-evals
/iblai-agent-skills        /iblai-agent-chat
/iblai-agent-safety        /iblai-agent-disclaimers
/iblai-agent-privacy       /iblai-agent-tools
/iblai-agent-mcp           /iblai-agent-tasks

Highlights: /iblai-agent-create creates an agent from a template; /iblai-agent-llm picks the LLM provider and model; /iblai-agent-datasets manages RAG training data (files, URLs, YouTube, crawl, GitHub); /iblai-agent-memory manages agent memories; /iblai-agent-safety and /iblai-agent-privacy cover moderation and PII redaction; /iblai-agent-evals runs evaluations with LLM-as-Judge and human scoring; /iblai-agent-tasks schedules recurring agent runs; /iblai-agent-mcp wires up MCP connectors with OAuth.

Organization skills (platform admin)

Org-wide administration:

/iblai-org                 /iblai-rbac
/iblai-management          /iblai-crm
/iblai-integrations        /iblai-notifications
/iblai-tokens              /iblai-invites
/iblai-scim                /iblai-billing
/iblai-features

Highlights: /iblai-management administers users, groups, roles, policies, teams, and alerts; /iblai-rbac covers roles, policies, and permission checks; /iblai-scim provides SCIM 2.0 directory provisioning; /iblai-billing handles credits, paywalls, checkout, and subscriptions; /iblai-tokens rotates Platform API Tokens.

Profile skills
/iblai-profile             /iblai-profile-metadata

The signed-in user's own profile (Basic, Social, Education, Experience, Resume, Memory) and a per-user, per-org metadata key-value store.

Content & discovery skills
/iblai-search              /iblai-course-create
/iblai-analytics           /iblai-catalog
/iblai-milestones          /iblai-credentials
/iblai-catalog-media       /iblai-catalog-invitations

Highlights: /iblai-search provides faceted discovery of agents and content plus personalized (RAG) recommendations; /iblai-analytics spans KPIs, users, topics, transcripts, costs, courses, and reports; /iblai-course-create drives the Course Creation API; /iblai-catalog manages courses, programs, pathways, and the skills/roles taxonomy; /iblai-credentials manages digital credentials and assertions.

Skills live in the repo's skills/ directory — read them, extend them, or write your own.

MCP Server

A hosted Model Context Protocol server — no local installation required — covers the one runtime capability the skills can't: actually talking to a deployed agent, with streamed responses, tool use, and RAG. Wire it up with /iblai-agent-chat (it writes the config from your .env token + a chosen agent), or add it manually.

Connect from Claude Code
claude mcp add iblai-agent-chat --transport http https://asgi.data.iblai.app/mcp/agent-chat/ --header "Authorization: Api-Token YOUR_API_TOKEN"
Connect from Claude Desktop / Cursor
{
  "mcpServers": {
    "iblai-agent-chat": {
      "transport": "streamable-http",
      "url": "https://asgi.data.iblai.app/mcp/agent-chat/",
      "headers": {
        "Authorization": "Api-Token YOUR_API_TOKEN"
      }
    }
  }
}
Skills vs the MCP server

The split is administer/use-via-REST vs chat at runtime. Skills do everything reachable over REST — creating and configuring agents, datasets, memory, users, roles, notifications, discovery, profiles, analytics, and reporting. The MCP server exists only for holding a live conversation with a deployed agent; if a skill covers an operation, there is no server for it.

Authentication

Everything authenticates the same way:

  • Base URL: https://api.iblai.app
  • Header: Authorization: Api-Token on every request
  • Org & username: from login.iblai.app/me — each organization you belong to shows its key (e.g. enterprise, iblai, or a UUID)
  • Api-Token: /iblai-login mints your first token from your signed-in session; afterward /iblai-tokens lists, creates, and rotates tokens. The secret is shown once.

Never commit .env — it is in .gitignore.

Quick Start

You need Node.js (for npx), a skills-compatible AI agent (Claude Code, Cursor, OpenCode, and 15+ others), and an ibl.ai account. No account yet? Sign up at ibl.ai/join — it creates your account and your organization.

Install the skills:

npx skills add iblai/api

Then connect your organization (it writes IBLAI_ORG, IBLAI_USERNAME, and IBLAI_API_KEY to .env):

/iblai-login

Every other skill then reads those values from .env and calls https://api.iblai.app with Authorization: Api-Token .

How It Fits With the Other Repos

iblai/api is the headless management layer of the ibl.ai open-source family: it operates the same backend that the sample applications run on and that the infra CLI deploys.

  • github.com/iblai/vibe — how to "vibe code" new applications on top of the ibl.ai backend (Next.js SDK + Claude Code skills; npx skills add iblai/vibe)
  • github.com/iblai/os — a complete sample application on the backend: the open-source AI agent platform running at os.ibl.ai, yours to fork and modify
  • github.com/iblai/lms — another complete sample application: an open-source skills intelligence platform (courses, competencies, credentials), yours to fork and modify
  • github.com/iblai/iblai-infra-cli — how to deploy the platform on your own infrastructure with Terraform + Ansible, given access to the backend images

Copyright © ibl.ai | support@iblai.zendesk.com