You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like this feature to be available in the settings.
The default value should be https://api.openai.com/v1, however, it should also allow the specification of custom values.
I would also like to see similar setting for Google Gemini API base, with default value https://generativelanguage.googleapis.com or https://generativelanguage.googleapis.com/v1beta.
This should not be a fixed option, as there may be a need to switch APIs dynamically.
Please note:
Different APIs typically do not use the same API keys.
Sometimes, certain APIs do not require API keys at all, and more importantly, passing a redundant value as an API key could potentially trigger an error.
The text was updated successfully, but these errors were encountered:
Please tell me more. Why would having the a default value in settings be useful?
How does that improve the ability to create new models for a given provider?
Uh.. It seems to me that we do not speak about the same matter.
I will try to explain further.
But why the base url?
What other endpoints are you thinking about using?
I am not thinking about other endpoints at all.
I mean quite opposite: there is only one possible endpoint (/chat/completion), but many variable base api urls possible.
Besides, it is quite common practice - to specify base url.
Because there are a lot of other services, that are compatible with OpenAI.
I would like this feature to be available in the settings.
The default value should be https://api.openai.com/v1, however, it should also allow the specification of custom values.
I would also like to see similar setting for Google Gemini API base, with default value
https://generativelanguage.googleapis.com
orhttps://generativelanguage.googleapis.com/v1beta
.This should not be a fixed option, as there may be a need to switch APIs dynamically.
Please note:
The text was updated successfully, but these errors were encountered: