> ## Documentation Index
> Fetch the complete documentation index at: https://agent-observability-docs.splunk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LLM providers

> Choose and configure the right LLM integration for the models you want to use in Luna Studio.

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

| Provider                        | Credential required |
| ------------------------------- | ------------------- |
| [OpenAI](#openai)               | OpenAI API key      |
| [Anthropic](#anthropic)         | Anthropic API key   |
| [Google Gemini](#google-gemini) | Google AI API key   |
| [Groq](#groq)                   | Groq API key        |

## Add an integration

<Steps>
  <Step title="Open Integrations">Go to the [Integrations page](/luna-studio/ui/integrations/overview).</Step>
  <Step title="Choose a supported provider">Select OpenAI, Anthropic, Google Gemini, or Groq. Disabled cards marked **Coming soon** cannot be configured.</Step>
  <Step title="Enter the API key">Use the key issued by that provider.</Step>
  <Step title="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.</Step>
</Steps>

<Note>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.</Note>

### OpenAI

Best for teams using OpenAI directly.

| What you'll need | Notes                                                                                                     |
| ---------------- | --------------------------------------------------------------------------------------------------------- |
| API key          | Starts with `sk-...`. Get it from [`platform.openai.com/api-keys`](https://platform.openai.com/api-keys). |

### Anthropic

Best for teams using Anthropic directly.

| What you'll need | Notes                                                                                                                 |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| API key          | Starts with `sk-ant-...`. Get it from [platform.claude.com/settings/keys](https://platform.claude.com/settings/keys). |

### Google Gemini

Use Gemini models through the Google AI API.

| What you'll need | Notes                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------- |
| API key          | Get it from [Google AI Studio](https://aistudio.google.com/apikey). The key commonly starts `AIza`. |

### Groq

Use open models through the Groq inference API.

| What you'll need | Notes                                                                                 |
| ---------------- | ------------------------------------------------------------------------------------- |
| API key          | Get it from the [Groq Console](https://console.groq.com/keys). The key starts `gsk_`. |

## 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.