Models & providers
Agents need a model to run on. A workspace gets one two ways:
- Provider connections (BYO keys) — you add your own Anthropic / OpenAI / OpenRouter key (or a Daytona account for compute). The key is consumed at the connect boundary, held in custody, and never readable back — listings show a last-4
keyHintonly. - Platform default models — models the platform itself provides, so a fresh workspace can dispatch an agent before connecting anything.
One list, two sources
GET /v1/organizations/{orgId}/agents/providers (optional ?provider= filter) returns the workspace's own rows first, then the platform catalog as synthetic connections. The ProviderConnection.source field tells them apart: "workspace" or "platform" — an absent source means workspace (rows predating the field).
Platform rows are recognizable at a glance:
| Field | Platform value |
|---|---|
id | apc_platform_<provider>_<slug> (e.g. apc_platform_anthropic_default) |
name | platform-<slug> |
status | Always verified |
createdBy | platform |
createdAt / updatedAt | The epoch sentinel 1970-01-01T00:00:00.000Z — a platform row has no lifecycle of its own |
keyHint | Last-4 of the platform key |
config | Carries defaultModel / baseUrl |
Names starting with platform- are a reserved namespace: POST …/agents/providers rejects such a name with the field error names starting with "platform-" are reserved for platform default models.
Selection: BYO-first
When a dispatch needs a model connection, the rule is deliberate and BYO-first:
- The connection the workspace's explicit setting names, if present and verified — a platform default model is nameable here too.
- Else the sole verified workspace key.
- Else the workspace key named
default. - Else — only when the workspace has no verified key at all — the first platform entry (list order; the catalog leads with its default).
- Else nothing: a workspace with several keys and no explicit selection refuses rather than picking one.
The platform default never silently overrides an ambiguous BYO setup — and an ambiguous BYO setup never silently spends the platform key. If you hold multiple verified keys, name one in settings.
In the console
The Profiles tab of the Agents surface renders both populations. Platform rows are read-only with a "Platform" pill — no verify, no disconnect, no edit; they exist as long as the platform catalog says so. Workspace rows carry the full lifecycle (verify, update, disconnect).