HasData charges five API credits for every Google Trends request, and those credits share one pool with SERP, Maps, and scraper tools. The free tier ships 1,000 credits, paid plans start at $49/month, and unused credits expire at renewal. This page isolates only HasData trend pricing: effective cost per query, what the credit multiplier does to your budget, and when a Google-only stack still loses to multi-source APIs.
HasData sits in the same lane as SerpApi: a pay-per-success API that proxies Google Trends into JSON. The headline numbers look cheap until the five-credit multiplier and shared pool are applied. This page covers only HasData trend pricing in 2026, not the full vendor comparison. For that, see the trend data API pricing comparison and the SerpApi Google Trends pricing breakdown.
HasData's pricing table lists the Google Trends API at five API credits per successful request. That is five times the one-credit charge SerpApi applies to the same engine class. The offset is that HasData's credit bundles are priced lower per credit on mid-tier plans.
| Plan | Monthly price | Credits included | Max Trends queries (5 credits each) | Marginal cost per Trends query |
|---|---|---|---|---|
| Free | $0 | 1,000 | ~200 | $0 |
| Developer | $49 | 40,000 | ~8,000 | ~$0.006 |
| Production | $99 | 200,000 | ~40,000 | ~$0.0025 |
| Big Data | $249 | 600,000 | ~120,000 | ~$0.002 |
These per-query figures assume every credit in the plan goes to Google Trends. That rarely holds. HasData's SERP APIs cost 10 credits per request; Maps and image endpoints cost five. A monitoring job that mixes Google Search and Trends on the same account dilutes the Trends-only math.
Credits are platform-wide, not siloed by product. A $49 Developer plan with 40,000 credits might spend 30,000 on Google SERP calls (10 credits each) and leave only 2,000 Trends queries for the month. HasData deducts credits only on successful responses, which matches SerpApi's pay-for-success model.
Unused credits expire at billing renewal. HasData's docs state explicitly that remaining credits do not roll over. For trend research with uneven weekly volume, expiry is often the largest hidden cost: a month with 500 Trends queries on an 8,000-query allowance still forfeits the rest.
Concurrency limits also scale with plan tier. The free tier allows one concurrent request; Developer allows 15; Production allows 30; Big Data allows 50. Batch keyword research that fires parallel requests will hit the free-tier wall quickly.
HasData exposes Google Trends through two surfaces:
docs.hasdata.com/apis/google-trends): structured JSON for interest over time, interest by region, related topics, related queries, and trending searches. Five credits per call.Parameters mirror what Google Trends accepts: q for the keyword (required), optional geo for country, optional region for sub-national interest-by-region cuts. Responses are JSON, not the relative 0-100 index alone; fields depend on the data type requested.
The free plan advertises 1,000 API credits with no credit card. For a Trends-only smoke test, that is roughly 200 keyword pulls per month. HasData also markets a 30-day trial of paid features without a card, but the standing free allocation is the 1,000-credit tier.
Throughput on free is one concurrent request. A script that queries 50 keywords sequentially at ~2 seconds each needs about 100 seconds per run; at daily cadence, 200 credits last roughly four months of daily 50-keyword scans, not a full month of heavy research.
SerpApi charges one credit per Google Trends request. On the $75/month Developer plan (5,000 searches), marginal cost is $0.015 per Trends query. HasData's $49 plan delivers about $0.006 per Trends query if the full credit pool goes to Trends. At 3,000+ monthly Trends queries with no SERP spillover, HasData's mid tier can undercut SerpApi.
The crossover flips when:
For a side-by-side of SerpApi's one-credit model, see SerpApi Google Trends API pricing.
HasData and SerpApi both stop at Google. A product launch brief that needs TikTok hashtag velocity, Reddit discussion growth, and Amazon search demand requires three separate integrations or three vendor contracts.
Trends MCP exposes Google Search, Google News, Google Shopping, YouTube, TikTok, Reddit, Amazon, npm, Steam, Wikipedia, news volume, news sentiment, app downloads, and 15 live trending feeds behind one POST endpoint and one MCP connection. The free tier allows 100 requests per day with no credit card. Paid plans use subscription allocations rather than per-engine credit silos.
The comparison is not "which Google proxy is cheaper per call." It is total cost to answer a cross-platform trend question. A workflow that needs one Google series costs less on HasData or SerpApi. A workflow that compares Google interest against TikTok and npm in one agent turn pays integration tax on Google-only vendors that multi-source APIs avoid.
curl --request GET -G \
--url "https://api.hasdata.com/scrape/google-trends/search" \
--data-urlencode "q=cursor ide" \
--data-urlencode "geo=US" \
--header "Content-Type: application/json" \
--header "x-api-key: YOUR_API_KEY"
Each successful response deducts five credits. Check remaining balance at app.hasdata.com.
HasData's Google Trends API is priced for teams that want JSON Trends output without maintaining scrapers and can keep SERP usage off the same credit pool. The five-credit multiplier and no-rollover policy are the two numbers to model before signing up. For Google-only steady state above ~2,000 queries/month, HasData often beats SerpApi on marginal cost. For mixed-platform research, the trends API pricing comparison and free trends API comparison cover the full stack.
FAQ