Workflow 1
Learning content assistance
Connect this capability to the academy context instead of managing it as a separate operational island.
K
Available
AI providers integration
Add Kimi to your academy AI provider choices
Connect a supported Kimi model through your provider credentials and use it in eligible AcademyLauncher AI workflows.
Avoid dependence on a single model vendor
Match providers to cost and workflow needs
Keep credentials replaceable as models evolve
Connected workflow
Bring your Kimi API key
K
Kimi
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Customer-supplied API key
Billing
API usage is billed by the provider
Control
Change provider or model family
What you can connect
Make Kimi part of the learner journey
Use the provider where it creates value while AcademyLauncher keeps the workflow connected to users, products, learning and operations.
Workflow 2
Information organization
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Supported agent workflows
Connect this capability to the academy context instead of managing it as a separate operational island.
Connection process
From provider account to academy workflow
The exact authorization fields vary by provider, but the ownership model remains clear throughout setup.
01
Choose the connection
Select Kimi from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the bring your kimi api key process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling Kimi for instructors, learners or live academy operations.
04
Stay in control
Monitor the provider account and rotate, revoke or replace the connection whenever your academy requires it.
Ownership and trust
A connection should remain understandable and reversible
Provider integrations are most useful when your team knows which account is connected, what it enables and how to remove or replace it.
- Customer-supplied API key identifies the connection
- API usage is billed by the provider
- Change provider or model family
- Access should be limited to supported academy workflows
The AcademyLauncher standard
Your connection—not a black box
AcademyLauncher connects the provider to a useful academy experience while preserving a visible path back to the account, credential and permissions behind it.
Read our product principlesRelated connections
Build the rest of the workflow
Connect Kimi
Put Kimi to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Avoid dependence on a single model vendor
Match providers to cost and workflow needs
Keep credentials replaceable as models evolve