SerpApi's Google Trends endpoint draws from the same monthly search pool as every other engine. One Trends query equals one credit, credits do not roll over at renewal, and the free tier caps at 250 successful searches per month. This page isolates only SerpApi trend pricing: what each plan buys, what expires, and when a trend-only stack costs less elsewhere.
SerpApi publishes list prices. The Google Trends endpoint is not priced separately. Every successful Trends call consumes one credit from the account's monthly search pool, the same pool that Google Search, Google Shopping, and YouTube Search draw from. Teams that budget for trend research often miss that detail until a keyword batch job drains credits meant for SERP monitoring.
For the broader vendor comparison, see the trend data API pricing comparison. This page stays on SerpApi only.
SerpApi's public plans (month-to-month, cancel anytime) price all engines equally. A Google Trends interest-over-time query and a Google Search query both cost one credit when the response succeeds.
| Plan | Monthly price | Included searches | Cost per search (if fully used) | Throughput cap |
|---|---|---|---|---|
| Free | $0 | 250 | $0.00 | 50/hour |
| Starter | $25 | 1,000 | $0.025 | 200/hour |
| Developer | $75 | 5,000 | $0.015 | 1,000/hour |
| Production | $150 | 15,000 | $0.010 | 3,000/hour |
| Big Data | $275 | 30,000 | $0.009 | 6,000/hour |
SerpApi's FAQ states that only successful searches count. Cached responses, errors, and failed requests do not deduct credits. Result set size does not change the charge: a Trends response with full timeline data and an empty result both cost one credit.
Trend research volume is spiky. A product launch week might need 400 keyword checks; a quiet week might need 30. SerpApi's billing cycle resets the included search count on renewal. Credits left unused at the end of a cycle are not automatically added to the next month's allocation.
SerpApi does offer two partial mitigations. Downgrading a plan moves remaining searches from the prior tier into an "Extra Credits" balance. Accounts can also enable Automatic Early Renewal, which triggers a new billing cycle once the monthly allocation is exhausted. Both options increase spend relative to steady usage; neither turns variable trend research into a flat per-query rate.
A team on the $25 Starter plan that uses 350 of 1,000 credits in March still pays $25. The 650 unused credits vanish at renewal unless captured via downgrade mechanics. For trend-only teams without other SerpApi workloads, that waste is the hidden cost behind the headline $0.025 per query.
SerpApi's Google Trends engine scrapes the Google Trends web interface and returns JSON. Typical fields include interest-over-time arrays, related queries, and geographic breakdowns. The Google Trends Trending Now engine returns live breakout queries. Data is relative (Google's 0-100 index), not absolute search volume.
That scope is sufficient for single-source Google monitoring. It does not include TikTok hashtag momentum, Reddit discussion volume, Amazon product search curves, or npm download trends. Each additional platform requires either another SerpApi engine (each costing its own credit) or a separate data vendor.
For a Google-only pricing view across pytrends, DataForSEO, and official alpha access, see Google Trends API pricing comparison.
These scenarios assume every query succeeds and no credits roll over. They isolate Google Trends calls only.
200 Google Trends queries per month. Fits the Free plan (250 credits) with 50 credits to spare. Cost: $0. Throughput cap (50/hour) becomes the bottleneck before credits do if all 50 keywords run in one batch.
600 queries if each keyword pulls interest-over-time and related queries as separate calls. Requires Developer plan ($75) or early renewal on Starter. Effective cost: $75/month minimum, $0.125 per keyword pair if the full 5,000-credit allocation is unused.
SerpApi alone cannot answer this in one call. Google Trends covers one source. Matching TikTok, Reddit, YouTube, and Amazon would need five integrations. Even at one query per source per brand per week, that is 400 queries/month on Google alone. Developer plan ($75) covers Google; the other four platforms need separate contracts.
Trends MCP prices by monthly request, not by engine. One request equals one source plus one keyword for historical series, or one live feed pull for top-trends mode. Public plans as of June 2026:
| Plan | Monthly price | Included requests |
|---|---|---|
| Free | $0 | 100 |
| Starter | $19 | 1,000 |
| Pro | $49 | 5,000 |
| Business | $199 | 25,000 |
The free tier requires no credit card. Google Search historical data and live Google Trends leaderboards are included. TikTok, Reddit, YouTube, Amazon, Wikipedia, and additional feeds share the same request pool and JSON response shape.
For the weekly SEO monitor (200 queries, Google only), SerpApi Free (250 credits) and Trends MCP Free (100 requests) diverge: SerpApi covers the volume on free tier; Trends MCP requires Starter ($19) or batching across two months. For the cross-platform brand tracker, Trends MCP covers five sources in five requests per brand per check; SerpApi covers Google only unless the team buys and wires four more vendors.
Neither tool is universally cheaper. The decision hinge is source count and credit waste, not the sticker price of the entry plan.
SerpApi fits teams that already pay for its Google Search, Shopping, or News engines and add Trends as a sidecar. The marginal cost of a Trends query is zero until the shared credit pool runs out. SerpApi also fits developers who need SERP scraping and Trends in one SDK with hour-level throughput guarantees on paid tiers.
SerpApi is a poor fit when trend research is the primary workload, volume is variable, or the questions require signals outside Google. In those cases, paying for a general SERP proxy to access one trend engine means overbuying capacity that expires unused.
For a feature-level comparison beyond price, see Trends MCP vs SerpApi for trend data. For free-tier limits across vendors, see free trends API comparison.
FAQ