← ClaudeAtlas

iblai-api-analyticslisted

Read ibl.ai analytics via the platform API — agent (chat) analytics, content (courses/programs/pathways/skills) analytics, org-wide KPIs, per-user learning data, and costs — plus generate and download Data Reports. Scope per-agent or organization-wide. Use to pull usage, engagement, cost, catalog, or per-user analytics.
iblai/api · ★ 15 · AI & Automation · score 75
Install: claude install-skill iblai/api
# iblai-api-analytics Read ibl.ai analytics from the platform API. One `/api/analytics/` family serves every scope; the query params decide what you get: - **Agent (chat) analytics** — add `mentor_unique_id` to scope any chat metric (topics, sessions, conversations, ratings, costs, transcripts) to one agent. - **Content analytics** — `/api/analytics/content/`, keyed by `metric=courses` | `programs` | `pathways` | `skills`, for catalog engagement and time spent. - **Organization-wide analytics** — omit `mentor_unique_id` for org totals. - **Per-user analytics** — a single user's enrollments, grades, time spent, engagement, and cross-platform snapshot. Reads are read-only; the only writes are Data Reports and a time-spent event. ## The schema is the contract These endpoints live on the **Data Manager** service and its live OpenAPI schema is the single source of truth — the URLs and params below exist for orientation and **can drift between releases**. Validate against the schema before building requests: - **Schema (raw):** `https://api.iblai.app/dm/api/docs/schema/` - **Swagger UI:** `https://api.iblai.app/dm/api/docs/` ```bash # Confirm the analytics paths you're about to call exist verbatim: curl -sS "https://api.iblai.app/dm/api/docs/schema/" -o /tmp/iblai_schema.yaml grep -nE "^ /api/analytics/" /tmp/iblai_schema.yaml ``` Treat any mismatch between this skill and the schema as a bug in the skill — the deployed schema wins. ## Auth & conventions - **`dm_url