English · 简体中文

Supported platforms

The Platform union in shared/types.ts (line 59) is the single source of truth for platform identity; the runtime registry in server/src/providers/index.ts must match it. The union currently declares 45 members:

• 43 built-in platforms registered as adapters at startup,
• plus the custom placeholder (a real OpenAI-compatible adapter built per API key, since its base URL is user-supplied), giving 44 entries in the registry map,
• plus sambanova, retained in the type union but no longer registered — it was dropped in V23 (June 2026) when its free tier was permanently retired (every chat call returns 402 "payment method required" once the one-time $5 trial credit lapses).

Of the 43 built-in platforms, 10 use dedicated adapters and 33 ride OpenAICompatProvider directly against a provider-specific base URL. Three platforms are registered keyless (kilo, ovh, and aihorde, which auto-configures with its documented anonymous sentinel key). The public catalog headline is smaller than the union because several registered gateways keep their free rosters in the hosted catalog rather than shipping them to every binary.

Catalog

Custom endpoint groups

Custom endpoints can be filed under a group you name (#1176): set it in the Group field when adding an endpoint, or later from Edit key. The group belongs to the endpoint, so every key in that endpoint's pool moves with it, and a key added later joins the same group. Blank means the default Custom (OpenAI-compatible) group.

• Keys page – each group gets its own section with a #handle badge (the label slugified: Work relays → #work-relays). The section's switch turns on or off only that group's endpoints.
• Requests – add the handle after a model id to keep a request inside the group: custom:deepseek-v3.1#work-relays (or deepseek-v3.1#work-relays) routes and fails over only across the group's endpoints that serve that model. An endpoint's own handle (custom:deepseek-v3.1#relay-a.example.com-v1) still pins a single endpoint and wins if a group has the same name.
• API – GET /api/keys returns groupLabel; PATCH /api/keys/:id and POST /api/keys/custom accept groupLabel ("" clears it); PATCH /api/keys/platform/custom accepts group (a label, or null for the ungrouped endpoints) to narrow the on/off sweep.

Related history

• Moonshot direct integration and MiniMax direct were dropped in migrateModelsV4 (paid-only / superseded by the OpenRouter route).
• Hugging Face was dropped in V4 ("tool-call format issues") and re-added in V13 through the Inference Providers meta-router.
• Chutes was evaluated for V11 and dropped: every model returned 402 requiring a non-zero balance, conflicting with the project's no-card criterion.