feat(search): add Tavily search provider - #95
Open
teionarr wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Adds TavilySearch alongside the existing Firecrawl/Brave/Bing/Google/DDGS providers, following the same Tool interface (List[SearchItem] -> ToolResponse), with search_depth defaulting to "basic" (1 credit) and opt-in "advanced". - Registered via @TOOL.register_module and exported from the search package - Wired into WebSearcherTool.search_tools (commented, matching the other key-requiring engines; enable by uncommenting + setting TAVILY_API_KEY) - Adds tavily-python to requirements.txt Also makes the existing TAVILY_API_KEY check in tests/test_report_tool.py meaningful, which previously had no Tavily provider behind it.
Copy link
Copy Markdown
Author
|
Hi 👋 — this adds TavilySearch alongside the existing search providers, following the same Tool interface as FirecrawlSearch. Motivation: tests/test_report_tool.py already requires TAVILY_API_KEY, but there was no Tavily provider behind it — this closes that gap. Verified against the live Tavily API (tavily-python 0.7.26); results map cleanly to SearchItem. Kept it commented in search_tools to match how the other key-requiring engines (Firecrawl/Bing) are handled — happy to make it active by default instead if you'd prefer. Open to any interface tweaks. |
Sorry, something went wrong.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds TavilySearch as a search provider alongside the existing Firecrawl / Brave / Bing / Google / DDGS backends.
Why
tests/test_report_tool.py already lists TAVILY_API_KEY as a required env var, but no Tavily provider existed in the codebase. This adds it, following the same Tool interface as the other search backends.
Changes
Notes
Testing
Verified against the live Tavily API (tavily-python 0.7.26): search returns correctly-mapped SearchItem results with populated title/url/content. The provider's src.* imports are identical to FirecrawlSearch.