Right now custom providers appear to support only one credential on the companion provider row, even though native providers already support multiple labeled keys.
It would be useful to extend that multi-key support to a single custom provider entry.
Use cases:
- one OpenAI-compatible custom endpoint with multiple API keys/accounts
- one Anthropic-compatible custom endpoint with multiple API keys/accounts
- avoid duplicating several near-identical custom provider entries just to store more than one key
- keep one custom provider definition (name/base URL/models) while managing several credentials under it
Suggested behavior:
- allow multiple labeled API keys for the same custom provider
- expose those keys in the custom provider UI
- support add/remove/rename/reorder for custom-provider keys, similar to native providers
- optionally allow future failover/rotation on auth/quota/rate-limit failure, but the first step is simply storing and managing multiple keys on one custom provider
This would make custom providers consistent with the existing multi-key support already available for native providers.
Right now custom providers appear to support only one credential on the companion provider row, even though native providers already support multiple labeled keys.
It would be useful to extend that multi-key support to a single custom provider entry.
Use cases:
Suggested behavior:
This would make custom providers consistent with the existing multi-key support already available for native providers.