SerpApi's Trending Now engine returns live breakout queries from Google's trending-now page. Each successful pull costs one credit from the shared monthly pool, cached responses within one hour are free, and throughput caps vary by plan. This page covers only that endpoint: request shape, response fields, polling math, and what the same live feed costs on Trends MCP.
Live breakout queries are the highest-churn trend data product. SerpApi exposes them through engine=google_trends_trending_now, and every fresh scrape costs one credit from the account's shared monthly pool. Newsrooms, growth teams, and alert bots that poll hourly need to model cache behavior and throughput caps before the first deploy, not after credits disappear mid-month.
For SerpApi's full Google Trends pricing across interest-over-time and autocomplete engines, see SerpApi Google Trends API pricing. This page stays on Trending Now only.
SerpApi scrapes Google's Trending Now page and returns JSON. A typical response includes a trending_searches array. Each item carries the query string, start_timestamp and end_timestamp for the breakout window, an active boolean, search_volume totals where Google surfaces them, and category tags.
The endpoint URL shape is:
GET https://serpapi.com/search?engine=google_trends_trending_now&api_key=YOUR_KEY
Optional parameters matter for billing. no_cache=true forces a live scrape and always costs one credit. The default (no_cache=false) allows SerpApi to serve a cached copy when the query and parameters match a request from the past hour. Cached responses are free.
SerpApi also supports async=true for deferred retrieval via the Searches Archive API. Async and no_cache should not be combined on the same request.
Trending Now draws from the same credit pool as Google Search, Google Shopping, and every other SerpApi engine. There is no separate Trending Now SKU.
| Plan | Monthly price | Included searches | Cost per fresh pull (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 |
Result count does not change the charge. A response with 25 trending queries and an empty response both cost one credit when the request succeeds.
The one-hour cache is the main variable in Trending Now budgets. Identical requests within 60 minutes return cached JSON at zero credit cost.
Four pulls per hour, 96 pulls per day, roughly 2,880 pulls per month if every call were fresh. With cache reuse, only the first pull each hour costs a credit. That drops to 24 credits per day and about 720 per month. Developer plan ($75, 5,000 credits) covers it with room for other engines.
Every pull is fresh. 96 credits per day, 2,880 per month. Requires Production plan ($150, 15,000 credits) with headroom, or Big Data ($275) if other engines share the pool.
Two fresh pulls per day, 60 per month. Fits Free tier (250 credits) with credits left for interest-over-time queries on the standard Google Trends engine.
Credits are not the only limit. SerpApi enforces hourly throughput by plan. Free accounts cap at 50 successful searches per hour. Starter allows 200 per hour. A burst script that fires 100 Trending Now pulls in five minutes on a Free account will throttle even if monthly credits remain.
For comparison across vendors, see the trend data API pricing comparison.
Trends MCP exposes live Google trending terms through get_top_trends with type: "Google Trends". One feed pull equals one request.
| Plan | Monthly price | Included requests |
|---|---|---|
| Free | $0 | 100 |
| Starter | $19 | 1,000 |
| Pro | $49 | 5,000 |
| Business | $199 | 25,000 |
The response returns ranked items with position and query text. The same tool call reaches TikTok Trending Hashtags, Reddit Hot Posts, YouTube Trending, and 15 other feeds without switching SDKs or response parsers.
For hourly Google-only polling with cache-equivalent behavior (one pull per hour), Trends MCP Free covers roughly 100 hours of coverage per month. SerpApi Free covers 250 fresh pulls regardless of engine, but only if throughput stays under 50 per hour.
SerpApi fits teams already on a paid SerpApi plan for Google Search or Shopping who want Trending Now as a sidecar. The marginal credit cost is zero until the shared pool empties. Teams that need breakout timestamps, category tags, and active flags in SerpApi's exact JSON schema also benefit from staying on-engine.
SerpApi is a poor fit when the workflow polls multiple platforms, needs more than 250 free pulls per month without a paid upgrade, or requires TikTok and Reddit breakouts in the same cron job. Each additional platform needs a different vendor or a second integration.
For a feature-level comparison beyond per-pull price, see Trends MCP vs SerpApi for trend data. For live-feed architecture patterns, see real-time trends API.
FAQ