Workflow 1
Long-form learning content assistance
Connect this capability to the academy context instead of managing it as a separate operational island.
C
Available
AI providers integration
Connect Claude to the academy tasks you approve
Use Anthropic Claude within supported AcademyLauncher workflows while keeping control of the API account, usage and enabled use cases.
Use another capable AI provider
Keep model access provider-independent
Apply human review to important outputs
Connected workflow
Bring your Anthropic API key
C
Anthropic Claude
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Customer-supplied API key
Billing
API usage is billed by Anthropic
Control
Decide where Claude is available
What you can connect
Make Anthropic Claude 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
Structured feedback drafting
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Knowledge and operations support
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 Anthropic Claude from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the bring your anthropic api key process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling Anthropic Claude 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 Anthropic
- Decide where Claude is available
- 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 Anthropic Claude
Put Anthropic Claude to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Use another capable AI provider
Keep model access provider-independent
Apply human review to important outputs