Serper vs SerpApi: which SERP API to buy in 2026

Buy Serper for prepaid Google SERP JSON. Buy SerpApi for a monthly multi-engine search API, a hosted MCP server, a one-hour cache that does not count against quota, and documented Google Trends engines. Neither product is a live multi-source trend board.

On 29 August 2026, Serper Starter was $50 for 50,000 credits ($1.00 per 1,000) at 50 queries per second. SerpApi Starter was $25 per month for 1,000 searches. That Starter ratio is 25 times, not the "up to 10 times cheaper" line on Serper's homepage. Trends MCP Starter is $19 per 1,000 requests for keyword growth and ranked feeds, with Cursor HTTP MCP on api.trendsmcp.ai.

Which SERP API wins each job?

Serper wins cheap Google JSON. SerpApi wins engine breadth, Legal Shield from Production, and first-party MCP. Trends MCP wins only when the agent needs growth series and live boards, not organic rankings.

Serper's homepage playground listed Search, Images, News, Maps, Places, Videos, Shopping, Scholar, Patents, and Autocomplete. That is Google-only depth. SerpApi's MCP page names Google, Bing, Yahoo, DuckDuckGo, YouTube, eBay, "and more," and the REST docs add google_trends plus google_trends_trending_now. Quote those named engines. Do not flatten third-party "80+" or "50+" counts onto either vendor.

Is Serper cheaper than SerpApi at every volume?

No. Serper is cheaper on a per-1,000 basis at every public pack against SerpApi Starter, and still cheaper against most of the monthly grid. The gap shrinks at SerpApi's high Cloud rows, and the products are not the same unit of work.

Serper published four prepaid packs on 29 August 2026 (serper.dev, accessed the same day). Credits last 6 months. Failed responses do not deduct; successful ones do.

Serper's FAQ states typical latency of 1 to 2 seconds, stretching to 2 to 4 seconds on retry, and says the API does not cache. Location is country plus language. Cards and PayPal are accepted. The homepage FAQ refund is a full refund within 7 days of the "initial credit purchase" unless more than 20% of credits are used. The terms page, last updated 29 May 2024, uses different wording: a refund request within 7 calendar days of the "first payment" for Serper API credits, and less than 20% of provided credits used. Those two sentences are not identical. Treat later top-ups as a support question, not a documented promise.

SerpApi published a month-to-month grid in USD on serpapi.com/pricing (accessed 29 August 2026). Only successful searches count. Cached, errored, and failed searches do not. Cache expires after 1 hour and cached searches are free. Throughput is guaranteed successful searches per hour.

Rows between Cloud 1M and Cloud 54M step by 1 million searches. Check the live grid for the step that matches volume. Speed modes multiply the base price: Best Effort is 1x (included), Ludicrous Speed is 2x, Ludicrous Speed Max is 4x. SerpApi states Ludicrous Speed as 2.2 times faster average response and 4.2 times faster p99 versus Best Effort, and Ludicrous Speed Max as 9.6% faster average and 35.4% faster p99 versus Ludicrous Speed. Those are relative claims, not millisecond SLAs.

Per 1,000 at named rows, using only the published price and search count: SerpApi Starter $25.00, Developer $15.00, Production $10.00, Searcher $7.25, Cloud 1M $3.75. Serper Starter $1.00 versus SerpApi Starter $25.00 is 25 times. Serper Ultimate $0.30 versus SerpApi Cloud 1M $3.75 is 12.5 times. The homepage "up to 10 times cheaper than competitors such as SerpAPI and Bright Data" is marketing copy, not a single verified ratio.

SerpApi's refund is a full refund within 7 days of the subscribe date unless more than 20% of searches are used. Plans can be upgraded, downgraded, or canceled; unused searches on a downgrade move to Extra Credits.

Trends MCP is a different SKU. The 29 August 2026 pricing.md table listed Free $0 / 100 requests, Starter $19 / 1,000, Pro $49 / 5,000, Business $199 / 25,000, with annual billing saving 20%. The HTML yearly toggle showed Starter $16 per month ($192 billed annually), Pro $39 ($468), Business $159 ($1,910), and copy "2 months free." Failed calls are free. Keyword alerts: Pro 50, Business 250. Do not treat a Trends MCP request as a SERP. get_growth is one source plus keyword (all periods in that call included). get_top_trends is one feed type per MCP call, counted per page of limit / offset.

Does Serper or SerpApi ship a first-party MCP server?

SerpApi does. Serper did not, on this fetch. Trends MCP does, with a different tool set.

SerpApi's hosted server is documented at serpapi.com/integrations/mcp (accessed 29 August 2026). Cursor / Claude Desktop JSON uses type: http and puts the key in the path. Auth can also be Authorization: Bearer. One main tool, search, defaults to engine google_light. Engine schemas are MCP resources (serpapi://engines and per-engine URIs). Opt-in MCP Apps tools search_table and search_dashboard exist for hosts that support SEP-1865. Markdown output is documented as cutting token usage by 50% on average, and by more than 90% for APIs with complex nested JSON.

{
  "mcpServers": {
    "serpapi": {
      "type": "http",
      "url": "https://mcp.serpapi.com/YOUR_SERPAPI_API_KEY/mcp"
    }
  }
}

Self-hosting clones github.com/serpapi/serpapi-mcp and points the same JSON at http://localhost:8000/YOUR_SERPAPI_API_KEY/mcp.

Serper's homepage and landing JavaScript on 29 August 2026 did not publish an MCP install block. The only mcp string in a loaded chunk was a third-party docs link (jan.ai/docs/mcp-examples/search/serper). https://serper.dev/docs returned HTTP 404. The in-page playground POSTs to https://google.serper.dev with path /w/{type}. Do not treat community wrappers or third-party POST /search plus X-API-KEY snippets as official Serper docs.

Trends MCP documents two hosts that are not interchangeable. Cursor uses Bearer on the API host. Claude.ai Connectors use OAuth on the www host. The Cursor block from docs.md (29 August 2026):

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Paste that into ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json). The matching landing page is the MCP server for Cursor guide. Windsurf uses serverUrl instead of Cursor's url plus transport. Three tools: get_time_series (~5 years weekly, one source plus keyword), get_growth (period presets, default ["12M"]), get_top_trends (type required on MCP). REST is POST https://api.trendsmcp.ai/api.

Who actually covers Google Trends?

SerpApi scrapes Google Trends as a SERP engine. Serper does not list a Trends type on the homepage. Trends MCP stores multi-source series and live boards so an agent does not fetch HTML.

SerpApi's Google Trends API (accessed 29 August 2026) requires engine=google_trends and q. TIMESERIES (default) and compared-breakdown-by-region accept up to 5 queries per search, comma-separated. Other data_type values accept 1 query. Date presets include now 1-H, today 12-m, today 5-y, and all (2004 to present). Property filter gprop can be images, news, froogle (Shopping), or youtube. Cache is 1 hour; cached searches are free. A separate engine, google_trends_trending_now, requires geo (the docs default that parameter when it is omitted) and optional hours of 4, 24 (default), 48, or 168.

That is still a scrape of Google's Trends UI. It is not TikTok hashtags, Amazon best-seller boards, Reddit hot posts, or Steam concurrent players.

Trends MCP is built for that second job. docs.md on 29 August 2026 listed 15 keyword sources for get_time_series / get_growth (google search, google images, google news, google shopping, youtube, tiktok, reddit, amazon, wikipedia, news volume, news sentiment, app downloads, app rankings, npm, steam) and 24 named live feeds for get_top_trends, including the four by Category boards. The same day's data-sources.md listed those 15 keyword sources and only 20 live feeds, omitting every by Category board. llms.txt said "plus 21 live feeds." The HTML pricing page marketed "35+ data sources." The MCP get_growth schema still lists python; the docs.md keyword table does not. Cite the split. Do not pick one number and pretend the others match.

Default get_top_trends limit is 25, max 200. sort=rank_change with window of 1d, 3d, 7d, 14d, or 30d returns climbers versus a prior snapshot. For Google Trends inside Cursor without a SERP key, the dedicated page is Google Trends MCP for Cursor. A side-by-side of Trends MCP versus SerpApi's Trends engine lives at Trends MCP vs SerpApi Trends.

HTML /pricing on this fetch also printed 9,515,253 API calls served. That counter moves during the day. It is a live marketing figure, not a quota.

When should a team buy both, or skip both?

Buy Serper alone when Google JSON is the only input, volume is bursty, and a 6-month credit expiry is acceptable. Buy SerpApi alone when Bing or shopping or flights or Legal Shield or a hosted MCP search tool is required, or when a one-hour cache will absorb repeated identical queries. Buy Trends MCP when the agent must ask "what is climbing on TikTok and Amazon this week" or "what is 12-month Google Search growth for this SKU," not "what are the current blue links for this query."

A common split is Serper or SerpApi for grounding and rank tracking, plus Trends MCP for the board and growth layer. That is two invoices. It is also two JSON shapes. Do not expect Serper credits to return a get_top_trends row, and do not expect a Trends MCP limit=10 Google Trends feed to include People Also Ask.

Skip all three if the need is a first-party Google Cloud Trends API with contractual access. This bake-off does not replace that path. Skip Trends MCP if the only output that matters is organic position, featured snippet HTML, or local-pack JSON. Skip Serper if the roadmap already includes non-Google engines. Skip SerpApi if the budget is a $50 prepaid pack and the workload is Google-only.

FAQ

Is Serper a drop-in cheaper SerpApi?

No. Pack pricing is lower. The surface is narrower. Serper's homepage listed ten Google search types. SerpApi MCP documents multiple engines and a search tool with per-engine schemas. A SerpApi Production plan also adds Legal Shield, which Serper does not sell on the homepage.

Does SerpApi MCP replace Trends MCP in Cursor?

No. SerpApi MCP is one search tool over SERP engines, default google_light, key in the URL path. Trends MCP is three read-only tools (get_time_series, get_growth, get_top_trends) with Bearer headers on api.trendsmcp.ai. Google Trends via SerpApi is engine=google_trends with a 5-query TIMESERIES cap. Google Trends via Trends MCP is a live type feed plus a keyword series on source google search.

How long do Serper credits last, and does SerpApi roll unused searches?

Serper credits are valid for 6 months on every paid pack published 29 August 2026. SerpApi is monthly; cancel keeps remaining searches until the renewal date, and a downgrade moves leftover searches to Extra Credits. Serper has no monthly unused-search rollover because there is no monthly quota.

Can Trends MCP return Google organic results the way Serper does?

No. Trends MCP returns 0-100 series, optional volume, growth percents, and ranked feed rows. It does not return organic title/link/snippet JSON. For that payload, Serper or SerpApi is the buy. Check current pricing on each vendor page before a contract, because both grids can move.

Sources

• Serper homepage pricing, FAQ, and playground, accessed 29 August 2026. Pack prices, QPS, 1-2s latency, no-cache claim, 2,500 free queries, "up to 10 times cheaper," 900,000+ companies line, and /w/{type} playground path.
• Serper terms, page JS last updated 29 May 2024, accessed 29 August 2026. Refund window tied to "first payment" and under 20% credit use.
• SerpApi pricing, accessed 29 August 2026. Monthly grid through Cloud 54M, speed-mode multipliers, Legal Shield / ZeroTrace / Priority Support flags, 7-day refund, cache and successful-search counting.
• SerpApi MCP, accessed 29 August 2026. Hosted JSON, search tool, google_light default, MCP Apps tools, markdown token-cut figures.
• SerpApi Google Trends API and Trending Now engine, accessed 29 August 2026. Five-query TIMESERIES cap, 1-hour cache, hours presets 4 / 24 / 48 / 168.
• Trends MCP first-party mirrors accessed 29 August 2026: pricing.md (plan table and 20% annual), HTML /pricing (9,515,253 API calls served; Free top 10 / 12 months / 24-hour delay / 35+ sources), docs.md (15 keyword sources, 24 live feeds, Cursor JSON, limit 25 / 200), data-sources.md (20 live feeds), and llms.txt (plus 21 live feeds).