/v1/models: return the full catalog with per-model availability + opt-in filter Split…
- User
/v1/models: return the full catalog with per-model availability + opt-in filter Split out from #242.
Current: `GET /v1/models` returns only models that are connected right now (enabled AND an enabled key can serve them).
Wanted: by default return the whole catalog (one entry per model id), each annotated with whether it's usable, plus an opt-in filter to get just the connected ones.
Per-model annotation:
- `available`: boolean — enabled AND a matching enabled key exists.
- `unavailable_reason`: `null` | `"no_key"` (enabled, no key) | `"disabled"` (catalog row disabled).
Filter:
- `?available=true` (alias `?connected=true`) → only connected models (the previous default behavior).
Notes:
- The extra fields are additive — OpenAI-compatible clients ignore unknown fields.
- Dedup prefers an available instance of a model id over a disabled/keyless one.
- The `auto` virtual model is always `available: true`.
Interface
No new interfaces are introduced.
- Assistant
I'll locate the current
/v1/modelsimplementation and how model availability is determined. - Assistant
Implementing the endpoint change and tests.
- Assistant
GET /v1/modelsnow returns the full catalog with per-model availability, and connected-only listing is opt-in.Behavior
Default — one entry per
model_id(deduped), plusautofirst:available:truewhen the row is enabled and a matching enabled key existsunavailable_reason:null|"no_key"|"disabled"- Dedup prefers an available row over disabled/keyless duplicates (same
intelligence_ranktie-break as before)
Filter —
?available=trueor?connected=truerestores the old behavior (only connected models)auto— alwaysavailable: true,unavailable_reason: nullChanges
server/src/routes/proxy.ts— rewrote the/modelshandler with a CTE-style query that annotates availability and supports the filtershared/types.ts— extendedModelListRowwithavailableandunavailable_reasonserver/src/__tests__/routes/proxy-models-catalog.test.ts— tests for full catalog, filter/alias, dedup preference, and uniqueness
All 10 related tests pass.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →