The guide · updated Oct 2026
How to choose a search API.
Ignore the leaderboards. Five questions decide it, and you probably know three of the answers already.
01 Who reads the results?
If a person reads them, you want fast, well-ranked links and snippets, so any independent index or SERP API will do.
If a model reads them, the snippet is rarely enough. You'll end up fetching every page, so pick an API that does
the fetching and cleaning for you, or plan to build that yourself.
02 What do you need back?
The four shapes are links, page text, a written answer and Google's exact results page.
They're different products, so don't compare their prices as if they were the same thing.
A $1 SERP call plus your own scraper can easily cost more than a $8 call that returns clean text.
03 Whose index is it?
This is the risk question. Microsoft retired the Bing Search APIs in August 2025. Google's Custom Search
stopped taking new customers, and its whole-web search ends on January 1, 2027. Google's suit against SerpApi
was dismissed in July 2026, but without prejudice, and Reddit's separate suit is still pending. Scraped-Google
APIs work today, and they also carry risk that isn't on the invoice.
04 What does it cost at your volume?
Work it out per useful result, not per call. Count retries, the extra fetches, and the tokens the results add to
every later turn of an agent loop. Built-in model tools look cheap until those tokens show up.
05 What can you do with the results?
Read the terms before you cache anything. Brave, for example, only allows storing results for training or
tuning on plans that explicitly grant storage rights. Built-in search from model vendors ties you to their models.
Yandex has different terms for non-residents of Russia and Kazakhstan.
Official list prices, checked on each vendor's pricing page on November 2, 2026. Click a name for its source. Work out your monthly bill →