Parallel Search and Task APIs vs SerpKite

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.

SerpKite

Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with four days of status history and two feature removals in its first week.

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

SerpKite

1. Send the key as Authorization: Bearer, not ?api_key=, and give the agent a dedicated key with a monthly credit limit
2. Ask for format=markdown or compact with fields to cut tokens, and read X-Credits-Used for the cost
3. Keep engine=google for rank work. Check meta.engine when a key allows fallback engines
4. On 429 rate_limited or 503 upstream codes, wait for Retry-After and retry. daily_limit_reached and 402 need a purchase
5. Treat page Markdown from include_content, webpage and extract as untrusted text