AI Providers

Connect your AI provider API keys to power your configurations. We support all major providers including OpenAI, Anthropic, Google AI, xAI, Mistral, Cohere, and DeepSeek.


Supported Providers

OP
OpenAI

GPT-4o, GPT-4 Turbo, GPT-4, GPT-3.5 Turbo

AN
Anthropic

Claude 3.5 Sonnet, Claude 3.5 Haiku, Claude 3 Opus

GO
Google AI

Gemini 1.5 Pro, Gemini 1.5 Flash, Gemini 1.0 Pro

MI
Mistral

Mistral Large, Mistral Medium, Mistral Small

CO
Cohere

Command R+, Command R, Command

DS
DeepSeek

DeepSeek Chat, DeepSeek Reasoner

Adding a Credential

  1. Navigate to API Keys from the sidebar or settings
  2. Click Add API Key
  3. Select your provider from the grid
  4. Fill in the required fields:
    • Name: A friendly name to identify this key (e.g., "Production OpenAI")
    • API Key: Your secret API key from the provider
    • API Endpoint: Auto-filled based on provider (customizable)
  5. Click Add API Key to save

Security

Your API keys are encrypted

All API keys are encrypted at rest using Rails' built-in encryption. We never display your full API key after it's saved—only a masked version.

Best practices for API key security:

  • Use separate API keys for development and production
  • Regularly rotate your API keys
  • Set usage limits on your provider's dashboard
  • Monitor your API usage for unexpected spikes

Custom Endpoints

For self-hosted models or alternative API endpoints, you can customize the API endpoint URL. Select "Custom Provider" when adding a credential to specify your own endpoint.

Custom endpoints must be compatible with the OpenAI API format for chat completions:

POST /v1/chat/completions
{
  "model": "your-model",
  "messages": [...],
  "temperature": 0.7,
  "max_tokens": 1024
}

Managing Credentials

From the API Keys page, you can:

  • Edit: Update the name or replace the API key
  • Activate/Deactivate: Temporarily disable a credential without deleting it
  • Delete: Permanently remove a credential (only if not used by any configurations)

Cannot delete credentials in use

If a credential is being used by one or more configurations, you must first update or delete those configurations before deleting the credential.