Expose a way to customize the path to the chat completions endpoint #369
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for PR! This can be achieved with a custom config which generates path - https://docs.rs/async-openai/latest/async_openai/config/trait.Config.html#tymethod.url Open to suggestion for a better design that works across all APIs instead of one off for chat completions! |
34 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some APIs are close to being compatible with this crate. The byot (bring your own type) feature is handy, but useless when the path is incompatible.
For example, Ollama's chat completions route is close to the OpenAI API but reachable on the
/api/chatroute. On the other hand, Claude (Anthropic) is available through the/v1/messagesroute, which is also very close to being compatible with the OpenAI API.