Workspace Model Routing

Configure per-workspace LLM providers so enterprise customers can bring their own API key.

Atlas supports workspace-level model routing. Each workspace can configure its own LLM provider and API key, overriding the platform default. This enables enterprise customers to use their own Anthropic, OpenAI, Azure OpenAI, or custom OpenAI-compatible endpoints.

SaaS Feature

Model routing is available on app.useatlas.dev Enterprise plans. Self-hosted deployments configure the model provider globally via environment variables.

Prerequisites

Managed auth enabled
Internal database configured (DATABASE_URL)
Active Enterprise plan on app.useatlas.dev
Admin role required for all model config endpoints
Encryption key configured (ATLAS_ENCRYPTION_KEY or BETTER_AUTH_SECRET) for API key storage

How It Works

Workspace model routing is opt-in per workspace. When no custom configuration exists, the workspace uses the platform default provider configured via ATLAS_PROVIDER and ATLAS_MODEL environment variables.

Resolution Order

When the agent loop starts a new conversation:

Workspace config (internal DB) — checked first if the user has an active organization
Platform env vars (ATLAS_PROVIDER / ATLAS_MODEL) — fallback when no workspace config exists

Supported Providers

Provider	Value	Description
Anthropic	`anthropic`	Claude models via `api.anthropic.com`
OpenAI	`openai`	GPT models via `api.openai.com`
Azure OpenAI	`azure-openai`	Azure-hosted OpenAI models (requires base URL)
Custom	`custom`	Any OpenAI-compatible endpoint (requires base URL)

Security

API keys are encrypted at rest using AES-256-GCM (same pattern as connection URLs)
API keys are never returned in API responses — only a masked version (last 4 characters) is shown
The encryption key is derived from ATLAS_ENCRYPTION_KEY or BETTER_AUTH_SECRET

Admin UI

Navigate to Admin > AI Provider in the admin console. From here you can:

View the current configuration (custom or platform default)
Set a custom provider, model, and API key
Test the connection before saving
Reset to platform default

Configuration Fields

Field	Required	Description
Provider	Yes	One of: Anthropic, OpenAI, Azure OpenAI, Custom
Model	Yes	Model identifier (e.g. `claude-opus-4-6`, `gpt-4o`)
API Key	Yes	Provider API key (encrypted at rest)
Base URL	For Azure/Custom	Endpoint URL for Azure OpenAI or custom providers

API Reference

All endpoints require admin role and enterprise license. Mounted at /api/v1/admin/model-config.

Get Configuration

GET /api/v1/admin/model-config

Returns the workspace's custom model configuration, or null if using platform defaults.

Response:

{
  "config": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "orgId": "org_abc123",
    "provider": "anthropic",
    "model": "claude-opus-4-6",
    "baseUrl": null,
    "apiKeyMasked": "***********api0",
    "createdAt": "2026-03-22T00:00:00.000Z",
    "updatedAt": "2026-03-22T00:00:00.000Z"
  }
}

Set Configuration

PUT /api/v1/admin/model-config
Content-Type: application/json

{
  "provider": "anthropic",
  "model": "claude-opus-4-6",
  "apiKey": "sk-ant-...",
  "baseUrl": null
}

Creates or updates the workspace model configuration. The API key is encrypted before storage.

Delete Configuration

DELETE /api/v1/admin/model-config

Removes the workspace's custom configuration. The workspace reverts to using the platform default.

Test Configuration

POST /api/v1/admin/model-config/test
Content-Type: application/json

{
  "provider": "anthropic",
  "model": "claude-opus-4-6",
  "apiKey": "sk-ant-...",
}

Tests a model configuration by making a minimal API call to the provider. Does not save the configuration.

Response:

{
  "success": true,
  "message": "Connection successful.",
  "modelName": "claude-opus-4-6"
}

Database Schema

The workspace_model_config table stores one row per workspace:

CREATE TABLE workspace_model_config (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  org_id TEXT NOT NULL UNIQUE,
  provider TEXT NOT NULL,
  model TEXT NOT NULL,
  api_key_encrypted TEXT NOT NULL,
  base_url TEXT,
  created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
  updated_at TIMESTAMPTZ NOT NULL DEFAULT now()
);

The org_id column has a unique constraint — each workspace can have at most one custom model configuration.