Adding Exa as a custom provider #10148
Closed
+163
−0
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
vercel-ai-sdk
bot
added
ai/provider
documentation
Collaborator
|
thanks for this @theishangoswami! given this is only covering the toolset, let's hold off merging as the community providers are designed for full provider implementations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Background
Exa is a web search API that lets developers add websearch tools to LLMs through the AI SDK. We created an npm package @exalabs/ai-sdk that provides a
webSearch()tool. This PR adds documentation for Exa as custom provider.Summary
Added documentation for the Exa community provider:
/content/providers/03-community-providers/102-exa.mdxwebSearch()toolThe documentation follows the community provider format with simple examples and a comprehensive options reference.
Checklist