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 first want to mention that I do not want to support OpenAI or want to enable them in any way. That is particularly why I want Mistral to succeed. That being said, their API function has become somewhat standard in a lot of libraries and projects. By changing the 'api_base' argument, you can point it at any url, given that they support that format and functionality. It would make things easier for people switching over codebases and also allow extra functionality, like generating using JSON mode or function calls with pydantic + instructor.
The text was updated successfully, but these errors were encountered:
I tested compatibility just now to try out using the Mistral API with https://github.com/jackmpcollins/magentic and found the allowed options for tool_choice was the only difference. I've opened a new issue specific to that #78
@j-dominguez9 Are there any other specific differences you are aware of? It looks like JSON mode has been added but I haven't tested this.
I first want to mention that I do not want to support OpenAI or want to enable them in any way. That is particularly why I want Mistral to succeed. That being said, their API function has become somewhat standard in a lot of libraries and projects. By changing the 'api_base' argument, you can point it at any url, given that they support that format and functionality. It would make things easier for people switching over codebases and also allow extra functionality, like generating using JSON mode or function calls with pydantic + instructor.
The text was updated successfully, but these errors were encountered: