Parallel Search and Task APIs vs SerpApi

Parallel Search and Task APIs

Fast-mode search at $1 per 1,000 with 10 excerpted results, and Extract at $1 per 1,000 URLs. Search defaults to advanced mode at $5 per 1,000 when mode is left out.

SerpApi

Over 100 engines behind one GET URL, with json_restrictor field selection and output=md. 25 incidents on the status feed from July to 1 October 2026, including an outage across all APIs on 10 September.

Parallel Search and Task APIs

1. Pass mode: "fast" on every search. Without it you pay the advanced rate
2. Create Task runs with max_retries=0 and check for an existing run before retrying
3. Give an objective plus two or three short search_queries. That's what ranks the excerpts
4. On 402, check available balance rather than total. Running tasks reserve credit
5. Prefer natural-language source guidance to domain filters. The docs say filters can cut result quality

SerpApi

1. Use the MCP with Authorization: Bearer, not the key-in-path URL the README leads with
2. Read serpapi://engines/<engine> before calling a new engine, since params isn't typed
3. Add json_restrictor or output=md to cut tokens, and mode: compact on the MCP
4. A 429 means either the hourly limit or an empty balance. Check the account before retrying
5. Repeat a search within the hour and the cached copy is free. Set no_cache=true only when freshness matters