Run

P0

a2cb16c686c39c37b0cf934d40e435970efdf18f

Agent context: I'll research the repository structure first to understand what it is and how it works. I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: total 80 drwxr-xr-x 8 user user 4096 Jun 6 04:48 . drwxr-xr-x 4 user user 4096 Jun 6 04:48 .. -rw-r--r-- 1 user user 376 Jun 6 04:48 .env -rw-r--r-- 1 user user 170 Jun 6 04:48 .git -rw-r--r-- 1 user user 50 Jun 6 04:48 .gitignore -rw-r--r-- 1 user user 5123 Jun 6 04:48 README.md -rw-r--r-- 1 user user 4119 Jun 6 04:48 app.py drwxr-xr-x 2 user user 4096 Jun 6 04:48 data drwxr-xr-x 2 user user 4096 Jun 6 04:48 embeddi Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 A simple local Retrieval-Augmented Generation (RAG) chatbot that can answer to questions by acquiring information from personal pdf documents. 2 3 (please, if you find this content useful please consider leaving a star ⭐) 4 5 ## What is Retrieval-Augmented Generation (RAG)? 6 <div style="text-align: center;"> 7 <img src="https://miro.medium.com/v2/resize:fit:1400/1*J7vyY3EjY46AlduMvr9FbQ.png" alt="rag_pipeline" wid Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 pypdf 2 langchain==1.1.3 3 langchain-core==1.2.5 4 langchain-community==0.4.1 5 langchain-chroma==1.0.0 6 langchain-text-splitters==1.0.0 7 numpy<2.0.0 8 chromadb # vector db 9 pytest 10 boto3 11 anthropic 12 openai 13 python-dotenv Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 VECTOR_DB_OPENAI_PATH='chroma-openai' 2 VECTOR_DB_OLLAMA_PATH='chroma-ollama' 3 DATA_PATH='data' 4 EMBEDDING_MODEL_NAME='openai' 5 LLM_MODEL_TYPE='gpt' 6 LLM_MODEL_NAME='gpt-4.1' 7 NUM_RELEVANT_DOCS='3' 8 OPENAI_API_KEY='YOUR_OPENAI_KEY_HERE' 9 CLAUDE_API_KEY='YOUR_CLAUDE_KEY_HERE' 10 11 # UNCOMMENT FOR LOCAL SETUP: 12 13 #EMBEDDING_MODEL_NAME=ollama 14 #LLM_MODEL_TYPE=ollama 15 #LLM_MODEL_NAME=llama3:8b 16 Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from flask import Flask, request, render_template, jsonify, redirect, url_for 2 from llm.llm_factory import LLMFactory 3 from retrieval.rag_retriever import RAGRetriever 4 from dotenv import load_dotenv, set_key 5 import os 6 7 load_dotenv() 8 9 VECTOR_DB_OPENAI_PATH = os.getenv('VECTOR_DB_OPENAI_PATH') 10 VECTOR_DB_OLLAMA_PATH = os.getenv('VECTOR_DB_OLLAMA_PATH') 11 LLM_MODEL_NAME = os.getenv('LLM_MODEL_NAME') # ' Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 import argparse 2 import os 3 import shutil 4 from embeddings.embeddings import Embeddings 5 from langchain_community.document_loaders import PyPDFDirectoryLoader 6 from langchain_text_splitters import RecursiveCharacterTextSplitter 7 from langchain_core.documents import Document 8 from langchain_chroma import Chroma 9 from dotenv import load_dotenv 10 11 load_dotenv() 12 13 OPENAI_API_KEY = os.getenv('OPENAI_API_K Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: /home/user/worktrees/attempt-725c1fbd-6745-4ed4-b392-f1cf0b23376e-cap-0/app.py /home/user/worktrees/attempt-725c1fbd-6745-4ed4-b392-f1cf0b23376e-cap-0/embeddings/embeddings.py /home/user/worktrees/attempt-725c1fbd-6745-4ed4-b392-f1cf0b23376e-cap-0/embeddings/openai_embeddings.py /home/user/worktrees/attempt-725c1fbd-6745-4ed4-b392-f1cf0b23376e-cap-0/llm/llm.py /home/user/worktrees/attempt-725c1fbd-6745-4ed4-b392-f1cf Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from llm.llm import LLM, GPTModel, OllamaModel, AnthropicModel 2 3 class LLMFactory: 4 @staticmethod 5 def create_llm(model_type: str, model_name: str, api_key: str = None) -> LLM: 6 if model_type == 'ollama': 7 return OllamaModel(model_name) 8 elif model_type == 'gpt': 9 return GPTModel(model_name, api_key) 10 elif model_type == 'claude': 11 return AnthropicModel(model_name, api_key) 12 else: 13 raise ValueError(f Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from abc import ABC, abstractmethod 2 from langchain_community.llms.ollama import Ollama 3 from openai import OpenAI 4 from langchain_core.prompts import ChatPromptTemplate 5 import anthropic 6 7 PROMPT_TEMPLATE = """ 8 Basing only on the following context: 9 10 {context} 11 12 --- 13 14 Answer the following question: {question} 15 Avoid to start the answer saying that you are basing on the provided context and go Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from langchain_chroma import Chroma 2 from langchain_core.documents import Document 3 from embeddings.embeddings import Embeddings 4 5 class RAGRetriever: 6 def __init__(self, vector_db_path: str, embedding_model_name: str, api_key: str): 7 self.vector_db_path = vector_db_path 8 embeddings = Embeddings(model_name=embedding_model_name, api_key=api_key) 9 self.embedding_function = embeddings.get_embedding_function() Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from embeddings.openai_embeddings import OpenAIEmbeddings 2 from langchain_community.embeddings.ollama import OllamaEmbeddings 3 from langchain_community.embeddings.bedrock import BedrockEmbeddings 4 5 class Embeddings: 6 def __init__(self, model_name: str, api_key: str = None): 7 self.model_name = model_name 8 self.api_key = api_key 9 10 def get_embedding_function(self): 11 if self.model_name == "ollama": 12 retur Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 from openai import OpenAI 2 3 class OpenAIEmbeddings: 4 """ 5 class that implements two methods to be called from Chroma 6 """ 7 def __init__(self, api_key: str): 8 self.client = OpenAI(api_key=api_key) 9 10 def embed_documents(self, texts: list[str]): 11 embeddings = [] 12 for text in texts: 13 response = self.client.embeddings.create(input=text, model="text-embedding-3-small") 14 embeddings.append(response.data[0 Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 import os 2 from dotenv import load_dotenv 3 from llm.llm import GPTModel, OllamaModel 4 from llm.llm_factory import LLMFactory 5 from retrieval.rag_retriever import RAGRetriever 6 7 load_dotenv() 8 9 VECTOR_DB_OPENAI_PATH = os.getenv('VECTOR_DB_OPENAI_PATH') 10 VECTOR_DB_OLLAMA_PATH = os.getenv('VECTOR_DB_OLLAMA_PATH') 11 LLM_MODEL_NAME = os.getenv('LLM_MODEL_NAME') # 'gpt-3.5-turbo', 'GPT-4o' or local LLM like 'l Agent context: I'll research the repository structure first to understand what it is and how it works. Provider mentions: openai

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: total 236 drwxr-xr-x 2 user user 4096 Jun 6 04:48 . drwxr-xr-x 8 user user 4096 Jun 6 04:48 .. -rw-r--r-- 1 user user 76740 Jun 6 04:48 alpha_society.pdf -rw-r--r-- 1 user user 74888 Jun 6 04:48 beta_society.pdf -rw-r--r-- 1 user user 74993 Jun 6 04:48 gamma_society.pdf Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: total 16 drwxr-xr-x 2 user user 4096 Jun 6 04:48 . drwxr-xr-x 8 user user 4096 Jun 6 04:48 .. -rw-r--r-- 1 user user 2458 Jun 6 04:48 admin.html -rw-r--r-- 1 user user 1488 Jun 6 04:48 index.html Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: total 24 drwxr-xr-x 3 user user 4096 Jun 6 04:48 . drwxr-xr-x 8 user user 4096 Jun 6 04:48 .. -rw-r--r-- 1 user user 4578 Jun 6 04:48 admin_settings.js drwxr-xr-x 2 user user 4096 Jun 6 04:48 demo_img -rw-r--r-- 1 user user 2215 Jun 6 04:48 styles.css Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: a2cb16c Merge pull request #4 from enricollen/dependabot/pip/langchain-core-1.2.5 c7e3ae7 Bump langchain-core from 1.1.3 to 1.2.5 b922a56 update README 6586c50 Merge pull request #3 from iscarth/docs-https-note d17c4dd Merge pull request #1 from iscarth/iscarth-patch-1 ab53cd8 docs(readme): add HTTPS deployment note 5876dc5 Merge branch 'main' of https://github.com/enricollen/rag-conversational-agent 392dbb3 minor fi Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 <!DOCTYPE html> 2 <html lang="en"> 3 <head> 4 <meta charset="UTF-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 6 <title>🤖 Chat with Documents</title> 7 <link rel="stylesheet" href="../static/styles.css"> 8 <script src="https://code.jquery.com/jquery-3.6.0.min.js"></script> 9 </head> 10 <body> 11 <div class="header"> 12 <h1>🤖 Chat with Documents</h1> 13 <a href="{{ url_for('admin') } Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: I'll research the repository structure first to understand what it is and how it works. Tool result summary: 1 <!DOCTYPE html> 2 <html lang="en"> 3 <head> 4 <meta charset="UTF-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 6 <title>⚙️ Admin Settings</title> 7 <link rel="stylesheet" href="../static/styles.css"> 8 <script src="../static/admin_settings.js"></script> 9 </head> 10 <body> 11 <h1>⚙️ Admin Settings</h1> 12 <form action="{{ url_for('update_settings') }}" method="POST" onsubmit="handleFo Agent context: I'll research the repository structure first to understand what it is and how it works.

Agent context: The repo is a Python/Flask LangChain RAG chatbot with OpenAI/Anthropic/Ollama backends. Now let me research the leading managed web-search providers by consulting their documentation. The repo is a Python/Flask LangChain RAG chatbot with OpenAI/Anthropic/Ollama backends. Now let me research the leading managed web-search providers by consulting their documentation. Provider mentions: openai

Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation. I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation.

Query/prompt: Extract details about Tavily's search API: what it does, how it's designed for LLMs/RAG, pricing/free tier, LangChain integration, Python SDK usage, and key features like answer generation and content extraction. Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation. Fetch prompt: Extract details about Tavily's search API: what it does, how it's designed for LLMs/RAG, pricing/free tier, LangChain integration, Python SDK usage, and key features like answer generation and content extraction. Tool result summary: # Tavily Search API Overview ## Purpose & Design Tavily Search is a REST API specifically engineered for LLM agents and RAG systems. The API executes search queries and returns ranked results optimized for AI consumption, including LLM-generated answers and cleaned content extraction. ## Core Capabilities **Search Functionality:** - Four search depth options balancing latency vs. relevance (basic, advanced, fast, ult Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation.

Query/prompt: Extract details about Exa's search/retrieval API: what it does, how it's designed for LLMs/RAG, neural/semantic search, pricing/free tier, LangChain integration, Python SDK usage, content retrieval and the answer endpoint. Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation. Fetch prompt: Extract details about Exa's search/retrieval API: what it does, how it's designed for LLMs/RAG, neural/semantic search, pricing/free tier, LangChain integration, Python SDK usage, content retrieval and the answer endpoint. Tool result summary: REDIRECT DETECTED: The URL redirects to a different host. Original URL: https://docs.exa.ai/reference/getting-started Redirect URL: https://exa.ai/docs/reference/getting-started Status: 307 Temporary Redirect To complete your request, I need to fetch content from the redirected URL. Please use WebFetch again with these parameters: - url: "https://exa.ai/docs/reference/getting-started" - prompt: "Extract details about Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation.

Query/prompt: best managed web search API for LLM RAG grounding 2026 Tavily Exa Perplexity Brave Linkup comparison Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation. Query: best managed web search API for LLM RAG grounding 2026 Tavily Exa Perplexity Brave Linkup comparison 10 search result links captured Tool result summary: Based on my search results, here's a comprehensive comparison of managed web search APIs for LLM RAG grounding in 2026: ## Top Contenders The top LLM search APIs in 2026 are Tavily, Brave LLM Context API, Exa, Perplexity API, and Google Programmable Search Engine (PSE), each optimized for different aspects of AI agent and RAG pipeline performance. ## Key Differentiators **Tavily**: Tavily is purpose-built for RAG pip Agent context: I'll research the leading managed web-search/retrieval providers in parallel, consulting their actual documentation.

Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates. Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates.

Query/prompt: Extract details about Exa's search/retrieval API: what it does, how it's designed for LLMs/RAG, neural/semantic search, pricing/free tier, LangChain integration, Python SDK usage, content retrieval and the answer endpoint. Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates. Fetch prompt: Extract details about Exa's search/retrieval API: what it does, how it's designed for LLMs/RAG, neural/semantic search, pricing/free tier, LangChain integration, Python SDK usage, content retrieval and the answer endpoint. Tool result summary: # Exa API Overview Based on the provided documentation, here's what Exa offers: ## Core Purpose Exa is described as **"a search engine made for AIs."** It's specifically designed to help artificial intelligence systems find precise web content. ## Key Functionalities The platform provides four main endpoints: 1. **Search** - Uses embeddings-based and intelligent search methods to locate webpages 2. **Contents** - Del Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates.

Query/prompt: Summarize the benchmark comparison of Tavily, Perplexity API, Google Search Grounding, and Exa. What were the quality, latency, and cost results? Which performed best for RAG grounding and why? Include any LangChain integration notes. Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates. Fetch prompt: Summarize the benchmark comparison of Tavily, Perplexity API, Google Search Grounding, and Exa. What were the quality, latency, and cost results? Which performed best for RAG grounding and why? Include any LangChain integration notes. Tool result summary: # Benchmark Comparison Summary ## Quality Results Perplexity API ranked first, followed by Exa in second place, Google Gemini Search Grounding third, and Tavily last. However, the benchmark used only eight ground-truth questions focused on recent factual events—a notably small sample size. The test prioritized local, time-sensitive queries like "when did AI Tinkerers Ottawa hold their last 2024 event," which favors p Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates.

Query/prompt: Does LangChain have an official Tavily integration? What is the package name and how is it used? Is it the recommended/featured search tool in LangChain? Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates. Fetch prompt: Does LangChain have an official Tavily integration? What is the package name and how is it used? Is it the recommended/featured search tool in LangChain? Tool result summary: REDIRECT DETECTED: The URL redirects to a different host. Original URL: https://python.langchain.com/docs/integrations/tools/tavily_search Redirect URL: https://docs.langchain.com/oss/python/integrations/providers/overview Status: 308 Permanent Redirect To complete your request, I need to fetch content from the redirected URL. Please use WebFetch again with these parameters: - url: "https://docs.langchain.com/oss/pyt Agent context: Let me consult Exa's actual docs (via the redirect) and the comparison/benchmark article, plus check LangChain integration support for the leading candidates.

Agent context: Let me confirm Tavily's LangChain integration package and free tier, since the repo is LangChain-based. Let me confirm Tavily's LangChain integration package and free tier, since the repo is LangChain-based.

Query/prompt: langchain-tavily official package TavilySearch tool free tier 1000 credits per month pricing Agent context: Let me confirm Tavily's LangChain integration package and free tier, since the repo is LangChain-based. Query: langchain-tavily official package TavilySearch tool free tier 1000 credits per month pricing 10 search result links captured Tool result summary: Based on the search results, here's what I found about the langchain-tavily package and TavilySearch tool pricing: ## Official Package & Tool Tavily ships a TavilySearchResults tool, and it's available through the langchain_tavily package with the `TavilySearch` class that can be imported and configured directly in your LangChain applications. ## Free Tier Pricing The free tier gives you 1,000 credits per month. A ba Agent context: Let me confirm Tavily's LangChain integration package and free tier, since the repo is LangChain-based.

Agent context: I have enough to make a well-grounded recommendation. Here's my analysis. ## Recommendation: **Tavily** For this repo specifically, Tavily is the best fit. ### Why Tavily for *this* codebase - **Native LangChain integration.** The repo is already built on `langchain-core`/`langchain-community`/`langchain-chroma`. Tavily ships an official `langchain-tavily` package (`TavilySearch` tool) and is LangChain's default search tool — it drops straight into the existing stack with minimal new code. - **Purpose-built for RAG, returns context not just links.** Tavily does search + scrape + filter + extraction in one call and returns cleaned markdown chunks with relevance scores. That maps almost 1:1 onto the existing `RAGRetriever.format_results()` pattern (`enhanced_context` + `sources`), so web results slot into the current Chroma-context flow with little plumbing. - **Fits the existing integration patterns.** The project already uses a factory + dependency-injected `api_key` + `.env` keys. Adding `TAVILY_API_KEY` and a web-search tool alongside the LLM/embedding factories is the same shape as what's there. - **Free tier to start:** 1,000 credits/month (1 credit/basic search), then $30/mo or $0.008/credit PAYG — low barrier for a local/personal RAG app. ### Alternatives I considered - **Exa** — strongest on neural/semantic search and full-page content; great for deep research, but more retrieval-engineering work and less of a turnkey "context block" output than Tavily. - **Perplexity Sonar API** — high answer quality in benchmarks, but returns *summarized answers* rather than raw retrievable context (fights this app's own LLM/prompt layer) and has a ~50 req/min cap that's not production-ready for agent loops. - **Brave Search / LLM Context API** — strong benchmark scores and clean markdown chunks at good pricing; the main downside vs. Tavily here is the weaker first-class LangChain story. - **Google Programmable Search / SerpAPI** — classic search APIs giving full control, but you build all the scraping/cleaning/ranking yourself. ### Documentation I actually consulted - **Tavily** — official API reference (`docs.tavily.com/.../endpoint/search`) and `langchain-tavily` / LangChain integration + pricing. - **Exa** — official docs (`exa.ai/docs/reference/getting-started`): search/contents/answer/research endpoints. - **Perplexity, Brave, Google Gemini Grounding** — via a head-to-head benchmark writeup (LLM-as-judge) rather than each vendor's raw docs. ### Why Tavily over the others Exa, Brave, and Perplexity can each beat Tavily on a given benchmark axis (semantic depth, freshness, answer quality), but for *this* repo the deciding factor is integration friction: it's already a LangChain RAG pipeline that formats retrieved chunks into context. Tavily is the one provider that is both LangChain-native *and* returns ready-to-use, scored context chunks — minimizing new code while matching the existing retrieval/factory/`.env` patterns. Perplexity's pre-synthesized answers and rate cap, and Exa's heavier retrieval engineering, make them worse fits despite strong standalone results. One caveat worth noting: Tavily was reportedly acquired by Nebius (2026) — no immediate impact, but worth tracking for pricing/terms changes. Sources: - [Tavily Search API docs](https://docs.tavily.com/documentation/api-reference/endpoint/search) - [Exa docs — getting started](https://exa.ai/docs/reference/getting-started) - [LangChain Tavily integration](https://python.langchain.com/docs/integrations/tools/tavily_search/) - [Compare Tavily, Perplexity, Google, Exa (benchmark)](https://websearchapi.ai/blog/compare-tavily-google-search-exa-perplexity) - [Brave — best web search APIs for AI 2026](https://brave.com/learn/best-search-api-2026/) Want me to implement it — add a `WebSearchTool` (Tavily) wired into the factory/`.env` pattern with a toggle to ground answers on web results alongside the PDF Chroma retrieval? I have enough to make a well-grounded recommendation. Here's my analysis. ## Recommendation: **Tavily** For this repo specifically, Tavily is the best fit. ### Why Tavily for *this* codebase - **Native LangChain integration.** The repo is already built on `langchain-core`/`langchain-community`/`langchain-chroma`. Tavily ships an official `langchain-tavily` package (`TavilySearch` tool) and is LangChain's default search tool — it drops straight into the existing stack with minimal new code. - **Purpose-built for RAG, returns context not just links.** Tavily does search + scrape + filter + extraction in one call and returns cleaned markdown chunks with relevance scores. That maps almost 1:1 onto the existing `RAGRetriever.format_results()` pattern (`enhanced_context` + `sources`), so web results slot into the current Chroma-context flow with little plumbing. - **Fits the existing integration patterns.** The project already uses a factory + dependency-injected `api_key` + `.env` keys. Adding `TAVILY_API_KEY` and a web-search tool alongside the LLM/embedding factories is the same shape as what's there. - **Free tier to start:** 1,000 credits/month (1 credit/basic search), then $30/mo o

I have enough to make a well-grounded recommendation. Here's my analysis. ## Recommendation: **Tavily** For this repo specifically, Tavily is the best fit. ### Why Tavily for *this* codebase - **Native LangChain integration.** The repo is already built on `langchain-core`/`langchain-community`/`langchain-chroma`. Tavily ships an official `langchain-tavily` package (`TavilySearch` tool) and is LangChain's default search tool — it drops straight into the existing stack with minimal new code. - **Purpose-built for RAG, returns context not just links.** Tavily does search + scrape + filter + extraction in one call and returns cleaned markdown chunks with relevance scores. That maps almost 1:1 onto the existing `RAGRetriever.format_results()` pattern (`enhanced_context` + `sources`), so web results slot into the current Chroma-context flow with little plumbing. - **Fits the existing integration patterns.** The project already uses a factory + dependency-injected `api_key` + `.env` keys. Adding `TAVILY_API_KEY` and a web-search tool alongside the LLM/embedding factories is the same shape as what's there. - **Free tier to start:** 1,000 credits/month (1 credit/basic search), then $30/mo or $0.008/credit PAYG — low barrier for a local/personal RAG app. ### Alternatives I considered - **Exa** — strongest on neural/semantic search and full-page content; great for deep research, but more