Manage connections to all LLM providers (OpenAI, Azure OpenAI, Azure AI Foundry, Vertex AI, etc.) in a single AI Provider section. Each connection is listed under AI Provider Connection Management, and you can configure multiple connections at once to balance load or expose a variety of models.
1
Add connection
Click the + button in AI Provider Connection Management and select the provider type.
2
Enter connection info
In the connection modal, enter API Base URL and API Key.
3
Verify connection
After saving, verify the model list auto-refreshes.
OpenAI
Azure OpenAI
Azure AI Foundry
Vertex AI
Setting
Description
API Base URL
https://api.openai.com/v1
API Key
Key from OpenAI (sk-...)
Prefix ID
Model ID prefix (optional — prevents collision in multi-connection)
Model IDs
Manual specification (auto-fetched if blank)
Setting
Description
API Base URL
https://{resource}.openai.azure.com/
API Key
Key from Azure Portal
API Version
API version (required, e.g., 2024-02-15-preview)
Prefix ID
Model ID prefix (optional)
Model IDs
Manual specification of deployed model names
Setting
Description
API Base URL
https://{project}.{region}.models.ai.azure.com/
API Key
Key from Azure AI Foundry
API Version
API version (default: 2024-05-01-preview)
Prefix ID
Model ID prefix (optional)
Model IDs
Manual (auto-fetched on Verify Connection if blank)
Azure OpenAI vs Azure AI Foundry
Azure OpenAI
Azure AI Foundry
Endpoint format
{url}/openai/deployments/{model}/...
{url}/openai/v1/...
Model identifier
Deployment name
Model ID
Auth (both take an API Key)
Sent as api-key + Authorization: Bearer
Sent as Authorization: Bearer only
Use
OpenAI-only models on Azure
Diverse models on Azure AI (OpenAI + OSS)
Azure OpenAI manages models per deployment; Azure AI Foundry accesses them directly from the model catalog. If you already use Azure OpenAI, Azure AI Foundry isn’t separately required — add it when you need OSS or Azure AI Foundry-only models.
Setting
Description
Project ID
Google Cloud project ID (required)
Location
Region (default: us-central1)
Auth
Global GCP Key or Custom Service Account JSON
Available models are auto-displayed on Verify Connection.
Test API access via the verify button in the settings modal
Prefix ID
Distinguish models with {prefix}.{model} form when names collide across connections
Activate/Deactivate
Per-connection toggle to pause without deleting
Model IDs
When manually specified, only those models are exposed. Auto-fetched if blank
Adding multiple connections to the same provider auto-merges model lists. For example, adding 2 Azure OpenAI connections (US/Korea regions) shows models from both regions. Use Prefix ID to distinguish.
Configure global cloud service accounts. Service Account Keys set here serve as fallback when individual features (TTS, STT, images) lack separate keys.
Provider
Settings
Google Cloud
Service Account Key (JSON)
Leaving Service Account Key empty uses Application Default Credentials (ADC).
Allow users to use Gmail sending, calendar event creation, and Drive document creation from chat. Each capability is controlled by an individual toggle, and actual use requires both a per-user Google OAuth connection and group permissions. For safety, all defaults are disabled.
Toggle
Scope
Review requirement
Gmail integration
gmail.send
Sensitive scope — requires Google App verification
Calendar integration
calendar.events
Restricted scope — requires CASA Tier 2 security audit
Drive integration
drive
Restricted scope — requires CASA Tier 2 security audit
Gmail, Calendar, and Drive fall under Google’s sensitive and restricted scopes. Complete App verification or CASA review before production deployment for these to work correctly.
