which search api have you already used?

if you asked cursor a question today, maybe you used exa. if claude searched the web for you, maybe you used brave. if a langchain agent looked something up, that might have been tavily. you have probably used atleast one of five retrieval apis this week.

why you should care which one sits under your agent

your answers inherit its blind spots. an agent cannot cite what its retrieval layer never found. the model gets the credit, but the index sets the ceiling — same prompt, different retrieval stack, different report. that gap is exactly what the blind battles here measure.

it's a concentration risk. llms are frozen at their training cutoff, so every web-aware agent needs a retrieval layer — and google doesn't license its index for this. microsoft retired the bing search api in august 2025; the endpoint now returns http 410 and the azure replacement costs 40–483% more. that pushed nearly the entire agent ecosystem onto the five vendors above. a repricing or outage at any one of them degrades a large slice of ai products at once.

they're not interchangeable. brave is a raw independent index. exa is semantic search over its own crawl. tavily is the plumbing inside agent frameworks. firecrawl turns arbitrary pages into llm-ready markdown. parallel is a full agentic research stack — and the only one on this list that also ships a finished deep research product, which is why four parallel variants sit on our leaderboard while the others power the products around it.

openai, gemini, and perplexity built their own crawl-and-index stacks — they're vertically integrated. almost everyone else's "web-aware agent" is a composition of the five vendors above. when you compare deep research providers, you're partly comparing retrieval layers; when you pick a search api for your own agent, you're picking your ceiling.

methodology & sources

compiled july 2026 from vendor customer pages, engineering blogs, and press coverage. a line appears only when the vendor or the customer has publicly named the relationship — anonymous "teams at" claims are excluded. many products use more than one api; absence of a line means undocumented, not unused. every row in the map's table view links to the page documenting that specific relationship.

• exa — customers & reviews
• exa vs tavily vs perplexity — search api comparison
• brave — search api growth
• brave — openclaw adoption
• brave — snowflake integration
• tavily — framework integrations
• tavily — langchain integration
• firecrawl — customer stories
• parallel — named customers, series b
• microsoft — bing search api retirement