Skip to main content
Use this page to choose one of the LLM providers that the Luna Studio UI can configure today.

​
When you need an LLM integration

Add an LLM integration when you want to:
  • Generate the training data for a run from a test set.
  • Label the training data with a LLM-as-judge prompt.
  • Compute the LLM-as-judge prompt’s F1 score against a selected test set.

​
Supported providers

​
Add an integration

1

Open Integrations

Go to the Integrations page.
2

Choose a supported provider

Select OpenAI, Anthropic, Google Gemini, or Groq. Disabled cards marked Coming soon cannot be configured.
3

Enter the API key

Use the key issued by that provider.
4

Save the integration

For an administrator’s first save, Luna Studio creates the workspace default. Non-admins save a personal override. Credential resolution is per provider: a personal key takes precedence for that provider, then its workspace default.
The source badge is attached to the shared LLM integration record. When personal and workspace credentials are mixed across providers, the badge might not describe the effective source of every provider key.

​
OpenAI

Best for teams using OpenAI directly.

​
Anthropic

Best for teams using Anthropic directly.

​
Google Gemini

Use Gemini models through the Google AI API.

​
Groq

Use open models through the Groq inference API.

​
Coming-soon providers

The catalog currently shows the following disabled provider cards as Coming soon:
  • Azure
  • Vertex AI
  • Mistral
  • NVIDIA
  • Databricks
  • Writer
  • AWS Bedrock
  • AWS SageMaker
  • Custom
These cards do not open a credential form and cannot be used as runtime LLM integrations in the current UI. A provider’s appearance in the catalog does not mean it is configurable.

​
Update or remove an integration

  • Update replaces the provider’s API key at the selected scope.
  • Remove deletes that provider’s personal override or, for an administrator managing a workspace-sourced card, its workspace default.
After a personal provider credential is removed, runtime resolution falls back to that provider’s workspace credential when one exists. Removing a workspace default does not delete other users’ personal overrides.