feat: add Tavily news vendor to tradingagents dataflow fallback chain#3
Open
tavily-integrations wants to merge 2 commits into
Conversation
added 2 commits
March 30, 2026 16:31
…w — add Tavily as third vendor in fallback chain
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
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.
Summary
tradingagents/dataflows/pipelinetavily_news.pywithget_news_tavily()andget_global_news_tavily()using the Tavily search API (topic="news")VENDOR_METHODSforget_newsandget_global_newsininterface.py"tavily"toVENDOR_LISTso it participates in the existing fallback routingFiles changed
tradingagents/dataflows/tavily_news.py(new) — Tavily news fetch functionstradingagents/dataflows/interface.py— import + register Tavily vendorrequirements.txt— addedtavily-python>=0.5.0.env.example— addedTAVILY_API_KEYandSKOPAQ_TAVILY_API_KEYDependency changes
tavily-python>=0.5.0torequirements.txtEnv var changes
TAVILY_API_KEYandSKOPAQ_TAVILY_API_KEYto.env.exampleNotes for reviewers
data_vendors.news_dataconfig key ortool_vendorsmaproute_to_vendor()fallback mechanism handles Tavily transparently🤖 Generated with Claude Code
Automated Review
tavily_news.pywith syncTavilyClient(appropriate for this synchronous routing context), registers both functions ininterface.py's vendor registry, adds comprehensive unit tests, updatesrequirements.txt, and documents env vars in.env.example. No regressions are introduced — the lazyTavilyClientimport inside_get_tavily_client()meansinterface.py's top-level import is safe even without the package installed. One minor inconsistency:env_bridge.pyis not updated to bridgeSKOPAQ_TAVILY_API_KEY→TAVILY_API_KEY(unlike all other provider keys), but.env.exampleexplicitly documentsTAVILY_API_KEY=as a direct env var, and the approved scanner-news-screener prerequisite uses the same pattern.