Implement proper Anthropic provider using its first-class API #153
Conversation
…ad of OpenAI compatibility layer.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
JasonTheAdams
left a comment
There was a problem hiding this comment.
Looks good overall! One question and a suggestion.
My question is whether the API URL should be changed for the provider or if it's actually exactly the same? I was surprised to not see that.
This is not necessary. It's the same API base URL, it's only the specific route that changes, which this PR does. |
Fixes #107.
This unlocks significant benefits, such as being able to use Anthropic's web search features, its recently introduced JSON output (boy, were they late to that party - but it's awesome!), as well as additional supported parameters that weren't possible to support via the OpenAI API compatible implementation.