Web Search / Web search APIs for RAG
Independent comparison · 2026

Best Web Search APIs for RAG (2026): Retrieval Accuracy, Speed & Cost

Best web search API for RAG by developer retrieval accuracy: Perplexity, 77.3% task completion in this benchmark. Fastest search: Parallel turbo, 333ms (64.7% task completion). Lowest recorded search price: TinyFish, $0.00 per 1,000 queries within its free-tier limits.

Compare web search APIs for retrieval-augmented generation using our developer retrieval benchmark, with accuracy, search speed and pricing per 1,000 queries. Compare 10 providers across 14 configurations, including Exa, Tavily, Brave, Parallel and Firecrawl, on the same questions.

Updated 20 September 2026. Last measured 15 September 2026.

Web search for RAG: retrieval accuracy, speed and cost

Task completion on 100 developer questions with the same agent using search results. Each task requires a passing patch and a citation from the run's sources. Search latency and total task latency are shown separately. Prices are the benchmark-recorded rate basis, with the same configurations used for the quality results.

100 questions · 14 configurations · ordered by task completion
RankProvider & configurationTask completionMean search timeRecorded $ / 1,000 queriesMedian task timeMedian task costOfficial docs
1Perplexitysearch_context_size=low/search77.3%957ms$5.00Search API · POST /search18.31s$0.06Official docs ↗
3Parallel fastmode=fast/v1/search66.7%953ms$1.00mode=fast · 10 results22.09s$0.05Official docs ↗
4Exa fasttype=fast/search66.3%626ms$7.00type=fast · up to 10 results19.97s$0.10Official docs ↗
5Parallel turbomode=turbo/v1/search64.7%333ms$1.00mode=turbo · 10 results18.69s$0.06Official docs ↗
6Exa instanttype=instant/search61.3%447ms$7.00type=instant · up to 10 results20.58s$0.10Official docs ↗
8Tavily basicsearch_depth=basic/search51.0%1.72s$8.001 credit · $0.008 PAYG26.40s$0.10Official docs ↗
9Nimblesearch_depth=lite · full_content=false · focus=general/v2/search46.7%3.15s$1.10search_depth=lite · full_content=false32.72s$0.04Official docs ↗
10Linkup fastdepth=fast · outputType=searchResults/v1/search43.3%1.39s$5.00depth=fast · searchResults26.76s$0.10Official docs ↗
11Nimblesearch_depth=standard · full_content=false · focus=general/v2/search42.3%878ms$5.00search_depth=standard · full_content=false25.27s$0.08Official docs ↗
12Youextraction_mode=highlights/v1/search41.3%596ms$5.00highlights included in Web Search23.93s$0.10Official docs ↗
13Youextraction_mode=highlights · knowledge=core/v1/search38.3%677ms$5.00highlights · knowledge=core · same Web Search price assumption21.05s$0.10Official docs ↗

From search result to a grounded RAG answer

Checks for each stage of a web-backed RAG application
StageKeep or measureHow to use this comparison
RetrieveQuery, endpoint mode, result URLs, passages and search latencyCompare the same search configurations and request times in the main table.
Select contextEvidence coverage, source diversity and tokens passed to the modelTest your chunking and reranking on the same retrieved results.
Generate and citeAnswer correctness and support for each cited claimDeveloper task completion measures successful evidence use in the tested agent. Evaluate your own answer format separately.
OperateSearch calls per answer, model spend and end-to-end timeKeep per-query search pricing separate from the full application bill.

For direct factual retrieval, also see the search accuracy comparison. For an agent that assembles evidence across many searches, see the multi-search comparison.

Choose the best web search API for your application

What this retrieval benchmark tells a RAG builder

The main table measures a developer agent that retrieves documentation and uses that evidence to solve a task. Accuracy here means grounded task completion: a patch must pass its checks and cite a source from the run. That is useful evidence for technical RAG and agentic retrieval. General chatbot answer quality still needs evaluation on your own questions and generation pipeline.

Keep the source attached to every retrieved passage

Retain the source URL, title, passage and retrieval time together. Feed evidence into the answer prompt with stable citation identifiers, then check whether each final claim is supported by its cited passage. A high search score is one part of this pipeline; chunk selection, context limits and the answer model also influence the result.

Compare retrieval latency with answer latency

Mean search time measures the API call. Median task time includes repeated searches and the agent’s work. For a RAG assistant, measure retrieval, reranking and generation separately, then track end-to-end time. Choose a configuration that meets the accuracy level your application needs before trading quality for a shorter response.

Estimate the cost of a grounded answer

Search cost per answer equals the number of search calls multiplied by the per-call price. Add input and output tokens, reranking and any scraping. The table separates recorded search price per 1,000 queries from median full-task cost, so a cheap API request and a cheap completed answer remain distinct.

Test the RAG pipeline on your own questions

Build a held-out set covering fresh facts, ambiguous questions, missing evidence and conflicting sources. Inspect retrieved passages, citation support and final answer correctness separately. Keep the model and prompt fixed while swapping search providers. Then test the chosen provider at your expected concurrency and context budget.

Benchmark method and source data

Task completion on 100 developer questions with the same agent using search results. Each task requires a passing patch and a citation from the run's sources. Search latency and total task latency are shown separately. Each row is one measured configuration. Missing measurements appear as a dash.

Open benchmark code ↗ · Public dataset sample ↗ · All benchmark methods →

Compare the developer search and search-plus-scrape boards →

Common questions

What is the best web search API for RAG?

Best web search API for RAG by developer retrieval accuracy: Perplexity, 77.3% task completion in this benchmark. Fastest search: Parallel turbo, 333ms (64.7% task completion). Lowest recorded search price: TinyFish, $0.00 per 1,000 queries within its free-tier limits.

Which benchmark does the main ranking use?

Task completion on 100 developer questions with the same agent using search results. Each task requires a passing patch and a citation from the run's sources. Search latency and total task latency are shown separately.

What does the price per 1,000 queries include?

The recorded search endpoint's request price. Model-token spend, optional scraping and plan conditions are separate. For rows with task measurements, median task cost is shown in its own column. Check the linked provider terms for current pricing.

Does this benchmark measure my complete RAG pipeline?

The main ranking measures grounded developer task completion with a fixed agent and search results. Use it to shortlist retrieval providers, then measure final answer correctness and citation support on your own RAG questions.

Related search API comparisons