Which search engines does SerpKite support?

Google (the default), Brave, Bing, Yahoo, DuckDuckGo and Yandex, plus Wikipedia as a consensus source. The providers reference lists which endpoints each engine serves.

Do I need accounts or keys for each engine?

No. One SerpKite key works for every engine. SerpKite reads each engine's public, logged-out results and isn't affiliated with any of them.

Do other engines return knowledge graphs and People Also Ask?

Only when that engine's page has an equivalent block. Brave, for example, often shows People Also Ask; Bing and DuckDuckGo results have organic results and related searches. Fields an engine doesn't have are absent.

Is a Google request ever answered by another engine?

Not unless you allow it. Without engine (or with engine: "google") a request stays on Google, unless your API key has fallback switched on in the dashboard.

engine=

Multi-engine search API

Google, Bing, Brave, DuckDuckGo, Yahoo and Yandex behind one key and one response shape. Change one parameter to switch engines, and every response says which engine answered.

Get a free API key Search providers reference

How it works

Google, Bing, Brave, DuckDuckGo, Yahoo and Yandex behind one key.

Most search APIs give you one index. SerpKite answers from Google by default, and the engine parameter switches the same request to Brave, Bing, Yahoo, DuckDuckGo or Yandex. The request body, the SDK call and the response keys stay the same: results[] with title, link, domain and snippet, and a meta object.

meta.engine always names the engine that produced the result, and meta.route lists every attempt with its outcome and duration. Results are never relabelled, and the cache never serves one engine's result to a request for another.

Every engine costs the same credits as Google, and failed, blocked and empty requests are free whichever engine you ask.

Same call, another engine

cURL

TypeScript

Python

curl https://api.serpkite.com/v1/search \
  -H "Authorization: Bearer $SERPKITE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q":"best espresso machine","engine":"brave"}'

Which engine serves which endpoint

Each engine maps into the same response shape. Verticals not listed for an engine are answered by Google only.

Which engine serves which endpoint
Engine	Index	Endpoints
Google (default)	Google	search, news, images, videos, maps, places, reviews, shopping, scholar, patents, autocomplete
Brave	Its own independent index	search, news, images, videos
Bing	Microsoft's index	search, news, images, videos
DuckDuckGo	Web largely from Bing; own news, image and video feeds	search, news, images, videos
Yahoo	Web largely from Bing	search, news
Yandex	Its own index and Yandex Maps (Russia, CIS)	search, maps, places, place by `oid`

Why it matters

What you get

One parameter

engine: "brave", "bing", "yahoo", "duckduckgo" or "yandex". Or a list, to allow only those engines.

Automatic fallback

engine: "auto" keeps Google first and moves on to the next engine only when Google fails.

Consensus

engine: "consensus" asks up to 3 independent indexes at once and ranks results by agreement.

Honest labels

meta.engine and meta.route say exactly which engine answered and what was tried.

Same price everywhere

Every engine costs the same credits as Google. You pay only for the engine that answered.

Same SDKs

The TypeScript, Python and Go SDKs and the MCP server take engine like any other parameter.

FAQ