Open workflowanalytics opened 2 weeks ago
Hi @workflowanalytics I don't plan to extend current library to support alternate vendors. If they comply with the OpenAI api, it should work out of the box with modifying the baseUrl
as you mentioned. In all endpoints, models can be passed with a string as well as an enum so that allows to use alternate models if they are available. However, as mentioned, no plans to support custom vendor-specific functionality.
Thanks, what I expected. I'll try it out on a few to see if its a viable approach.
On Sunday, June 16th, 2024 at 4:24 PM, Stefan Bratanov @.***> wrote:
Hi @.***(https://github.com/workflowanalytics) I don't plan to extend current library to support alternate vendors. If they comply with the OpenAI api, it should work out of the box with modifying the baseUrl as you mentioned. In all endpoints, models can be passed with a string as well as an enum so that allows to use alternate models if they are available. However, as mentioned, no plans to support custom vendor-specific functionality.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
A number of vendors support the OpenAI api. It appears this is doable with your implementation as there is support for a URL 'connectTo' parameter. Will this SDK support use with alternate vendors that implement the OpenAi api faithfully?