Learning Studio / agents

Authenticate integrations

Every integration acts with the caller’s permissions.

Choose a connection

Use MCP for a compatible assistant, or HTTP for a custom integration. The app exposes /mcp and /api/public/agent on its own origin, not on this documentation domain.

MCP uses the app’s OAuth flow. Complete sign-in and consent in the compatible client. HTTP requests carry a valid signed-in user access token in the Authorization header.

Authorization: Bearer <user access token>

A publishable project key is not a user access token. The API verifies the user and applies row-level permissions as that caller. A course ID alone grants no access.

Start read-only

Call discovery or list courses, select the intended course, and read its current version before proposing a write. Treat missing or inaccessible courses as unavailable rather than trying to bypass their ownership.