DeepSeek Search and Fetch API vs Serper

DeepSeek Search and Fetch API

Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.

Serper

$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.

DeepSeek Search and Fetch API

1. Keep query to 128 characters and put filters in it as operators, such as site:github.com lang:en after:2026-01-01
2. Leave need_content false and read summary first, then call Fetch on the URLs you keep
3. Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented
4. Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown
5. Don't send private queries or an end user's IP in localization. Data is stored in the PRC

Serper

1. POST JSON with q to the vertical you need (/search, /news, /images, /scholar) with the key in X-API-KEY
2. Set gl and hl, since Google results vary by country and language
3. Pair it with a fetcher. Serper returns links and snippets, not page text
4. Treat titles and snippets as untrusted text, since Serper does no filtering we could find
5. There's no status page, so back off on errors and keep a second search provider