Run several providers and fall back when one fails
Four or more companies' docs show a full fit.
What counts as done
A merged, deduplicated result list, or a successful result from a second provider after the first returns 429 or a quota error, with no 400 or 401 treated as a fallback trigger.
How agents ask for it: use whichever search works
, merge results from a few engines
, if Brave is out of quota use Tavily
Does the job 4
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Exa API + MCP B Exa Labs Inc. | 402 and 429 (with Retry-After) are distinct, x402 on /search and /contents gives a keyless route, and one user fuses Exa with Tavily and SearXNG. source |
| SerpKite BB Anastasia Klimova, trading as SerpKite | engine=auto or a list such as google,brave falls back across engines inside one call, and 429, 402, 403 and 503 are distinct, with 503 never billed and safe to retry. source |
| SpecStream B SpecStream SAS | Drop-in addresses answer calls written for Tavily, Exa, Brave, Serper, Bing v7, Google CSE, SearXNG and Firecrawl in each API's reply shape, and 401, 402, 403 and 503 are distinct with 503 not charged. source |
| You.com APIs BB SuSea, Inc., d/b/a you.com | A keyless MCP profile, 429 with Retry-After and rate-limit headers, and a spend_cap_exceeded code distinct from rate limiting. source |
Does the job, with a limit 17
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Web Search Tool on Amazon Bedrock AgentCore BB Amazon Web Services, Inc. (regional AWS entities by account location) | No error responses are documented for the tool, so a host cannot tell a throttle from an empty result from the docs; auth is IAM or JWT through a gateway, not a plain key. source |
| Brave Search API + MCP B Brave Software, Inc. | A 429 is distinct and carries rate-limit headers, but keys are required (the x402 proxy is gone) and OpenClaw users hit a daily cap of about 1,000 with an expired token leaving no search at all. source |
| Cloudflare Web Search API B Cloudflare, Inc. | Three providers behind one endpoint, but the caller picks provider per request; nothing falls back on a provider error, and a missing BYOK key fails with 400. source |
| Kagi Search API C Kagi Inc. | A 429 means rate limited or usage limit exhausted with no Retry-After documented, and a paid key is required. source |
| Liner Search MCP E Liner | 429 carries Retry-After, but a key is required and no keyless or free route exists. source |
| Linkup B Linkup Technologies SAS | A 429 means rate limit exceeded or insufficient credits, one code for two causes; x402 gives a keyless fallback at $0.01. source |
| Mojeek Web Search API F Mojeek Limited | Errors such as Daily Limit Reached arrive as response.status text in a 200, so a host keyed on HTTP codes never sees a quota error. source |
| NewsCatcher B NewsCatcher, Inc. | 429 carries Retry-After and only successful work is charged, but a key is required and the corpus is news only. source |
| Parallel Search and Task APIs BB Parallel Web Systems Inc. | 429 on rate limits and 402 on balance are distinct, but the request needs an objective plus search_queries, a different shape from other providers. source |
| Perplexity Search API BB Perplexity AI, Inc. | 429 carries Retry-After and error.type names the limit, but no free or keyless route exists; an OpenClaw user with paid-only Perplexity was left with no search. source |
| SearchAPI.io D SearchApi, LLC | 401 and 429 are distinct JSON errors, but a key is required and there is no keyless route. source |
| SerpApi B SerpApi, LLC | A 429 covers the hourly limit and an empty balance alike, and the key is a query parameter; one user wanted it as a SearXNG fallback and could not. source |
| Serper F Serper | No error reference exists, so a host cannot know how quota or rate errors are signalled; the key goes in X-API-KEY. source |
| SERPHouse E Patoliya Infotech LLP | Errors can arrive as a 200 with status error, and 429 has no Retry-After guidance; the hosted MCP takes the key in its URL path. source |
| Tavily API + MCP A AlphaAI Technologies Inc. dba Tavily | 429, 432, 433 and 434 are distinct and 429 carries Retry-After, but the keyless cap arrives as natural-language text, which over MCP lacks isError, so a fallback may never fire. source |
| TinyFish Search B Tiny Fish, Inc. | 429 and 402 codes are distinct and the search is free, but the docs and pricing page disagree on what happens past the daily allowance. source |
| Valyu BB Valyu.Network Ltd | 429 with retry_after and 402 with insufficient_credits are distinct and never charged, but a key is required. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| DeepSeek Search and Fetch API C Hangzhou DeepSeek Artificial Intelligence Co., Ltd. | Error semantics not read; no account on fallback. |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Arcmira B Arcmira, Inc. | Not a web search provider, so it cannot stand in for one. |
| Grounding with Bing Search B Microsoft Corporation | Runs only inside a Foundry Agent Service model run and returns an answer, so it cannot be merged with or fall back to another provider's results. |
| Fetch (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | Not a search provider. |
| Grep AI B Parcha Labs, Inc. | Not a web search provider. |
What stops agents finishing
- quota error returned as plain text without isError, so the fallback never fires (Tavily keyless over MCP)
- provider selection bugs in the host (OpenClaw)
Around it
After: search.ground-fact.
Where this comes from
Weight 7 of 100 in Web search APIs: 6 of 44 accounts: a user fusing Exa, Tavily and SearXNG, a merged MCP, OpenClaw users asking for Brave-to-Tavily fallback, a quota-routing wrapper, a unified TypeScript package
The same as data: /api/v1/use-cases/search.multi-provider.json, or the MCP tool get_use_case with id search.multi-provider. Other jobs in this category: /api/v1/niches?category=search.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.