Oxagen Docs

How to set workspace-level model defaults for Content Studio at Settings → Models.

Workspace defaults control which model powers each generation tier for all runs in a workspace. A workspace owner sets defaults once at Settings → Models; individual generations can then override the tier on a per-message basis.

Navigating to model settings

Open the workspace sidebar.
Select Settings at the bottom of the sidebar.
Click Models in the settings navigation.

The Models settings page has three sections: API Keys, Models, and Embeddings.

Setting a default model per tier

The Models section lists three tier dropdowns:

Tier label	Internal tier	Default when no override
Oxagen	`level_1`	Platform default — Oxagen managed
Oxagen+	`level_2`	Platform default — Pro plan required
Oxagen+ Pro	`level_3`	Platform default — Pro plan required

Each dropdown lists every model available for that tier from the workspace catalog. The catalog includes:

Oxagen-managed models (the platform chooses the specific version)
Models from connected providers — visible only after adding an API key for that provider under API Keys

To set a default:

Click the dropdown for the tier you want to configure.
Select a model. The option labeled Oxagen managed delegates the choice to the platform.
Click Save. The new default takes effect on the next generation run.

Leaving a tier set to Oxagen managed means the platform selects the model. This is the recommended setting unless you have a specific version requirement.

Plan requirements

Tier 2 and Tier 3 models require a Pro plan. The tier dropdown shows a lock icon on gated options when the workspace is not on Pro; selecting a locked option has no effect while on the Free plan. Upgrade the workspace plan at Settings → Billing before configuring a gated tier.

Scope

Workspace defaults apply to all generation runs in the workspace, including runs triggered via the REST API and MCP tools, unless those calls pass an explicit model_selector value. When model_selector is provided on a run or message, it takes precedence over the workspace default.

The model selector hierarchy, from highest to lowest precedence:

model_selector value on the individual run or message
Workspace tier default set in Settings → Models
Platform Oxagen-managed default

REST API: reading and updating model configuration

Read the current configuration

GET /v1/workspace-models/catalog
Authorization: Bearer <api-key>

Returns the full model catalog annotated with the workspace's current tier assignments, BYOK availability, and plan gating.

Update tier assignments

PATCH /v1/workspace-models/workspace/model-config
Authorization: Bearer <api-key>
Content-Type: application/json

{
  "level_1_model_id": "claude-haiku-4-5-20251001",
  "level_2_model_id": null,
  "level_3_model_id": null
}

Setting a field to null reverts that tier to Oxagen managed. All model IDs must be present in the workspace catalog; unknown IDs return 422 Unprocessable Entity. Only workspace Owners can call this endpoint — Members receive 403 Forbidden.

Workspace Defaults