-
-
Notifications
You must be signed in to change notification settings - Fork 148
[Platform] Add support for Scaleway Responses API #1183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
8e6d77d to
01fa940
Compare
| --- | ||
|
|
||
| * Add the bridge | ||
| * Add support for Responses API |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * Add support for Responses API |
not needed for the first release
| * Allow beta feature flags to be passed into Anthropic model options | ||
| * Add Ollama streaming output support | ||
| * Add multimodal embedding support for Voyage AI | ||
| * Use Responses API for Scaleway platform when using gpt-oss-120b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please revert this line
|
Hi @daFish, what's the benefit of introducing this? feels a bit odd to have both, a lot of duplicated code and only fixed for one model so ideally we should decide for one API here to ease the implementation |
Scaleway currently supports both but to use From the Scaleway documentation:
As the responses API is currently in beta, I'd opt to support both for the time being. Once it is GA then it is the best option to move to responses API only. |
Thanks to the work by @paulinevos I am adding support for the Responses API from Scaleway. I also added 2 new examples to show use the responses endpoint - one with tool usage.