Trends data API for AI agents: from $0.001 per call ($1 per 1,000), no subscription
Whizbrew's Trends data API costs from $0.001 per call ($1 per 1,000 calls); a typical call is $0.001 ($1 per 1,000). Only a call that returns data is charged: an empty or failed call is free. There is no subscription and no monthly fee. A new account starts with $2 of free credit, with no card.
It reads public Trends data: 14 tools, live at the moment of the call, over one API key or one MCP server (https://whizbrew.com/mcp). It is an API, not a scraper you run: no proxies, no browser and no scraping code on your side. The same key reaches 893 tools for other platforms (all APIs, all tools, pricing).
Pricing
| Tool | What it returns | Per call that returns data | Per 1,000 calls |
|---|---|---|---|
trends.sounds | Trending sounds right now. | $0.005 | $5 |
trends.prediction_markets | What people bet will happen: open prediction markets with each outcome's price (0 to 1), traded volume and price change. | $0.001 | $1 |
trends.google_daily | Searches that are trending today in a country, with the size of the jump and the news stories behind each one. | $0.001 | $1 |
trends.wikipedia_views | Daily readers of one Wikipedia article: a free signal of how much attention a brand, product, person or topic gets over time. | $0.001 | $1 |
trends.wikipedia_top | Most read Wikipedia articles of one day, for a country (all languages read there) or for one language edition. | $0.001 | $1 |
trends.pinterest | Search terms trending on Pinterest in a country, with interest (0 to 100) and the change over a week, a month and a year in percent (10000 means 10,000 % or more). | $0.001 | $1 |
trends.netflix_top10 | Netflix weekly Top 10. Without a country: the global lists with hours viewed and views, any week since 2021-07-04. With a country: that country's films and TV lists (ranks only). | $0.001 | $1 |
trends.google_interest | Google Trends search interest for a search term: the curve over time (0 to 100, 100 = the peak of the period) and the regions where it is searched most. Up to 5 comma-separated terms are compared on one scale. Values are relative, not search counts. A term with too few searches answers with empty lists. Answers are cached for 10 minutes. | $0.002 | $2 |
trends.google_related | Google Trends related searches for one search term: the top queries people also search (0 to 100) and the rising ones with their growth ("+250%", or "Breakout" for a query that barely existed before). Up to 25 of each. A term with too few searches answers with empty lists. Answers are cached for 10 minutes. | $0.002 | $2 |
trends.naver | Search interest on NAVER, South Korea's largest search engine, for 1 to 5 keywords: one point a day, by default for the last 365 days. Values are relative (0 to 100): 100 is the busiest day of the busiest keyword in the request, so they compare only within one answer and are not search counts. Each series has its average and peak day. Optional date range (from 2016-01-01, at most 731 days) and visitor filters (device, gender, age groups). Daily points only (no weekly or monthly unit); South Korea only; a keyword nobody searched comes back with no points. | $0.002 | $2 |
trends.naver_shopping | The most searched keywords of a NAVER Shopping category (South Korea): the top 500 for a date range, 20 a page. Ranks only: the source gives no search counts. Default range is the last 30 days; at most 365 days, from 2017-08-01. Optional visitor filters (device, gender, age decades). Category ids come from trends.naver_shopping_categories (e.g. 50000003 = digital/appliances); an id the source does not know answers an empty list. Keywords are in Korean. | $0.001 | $1 |
trends.naver_shopping_categories | The category tree of NAVER Shopping (South Korea): the children of one category, with the ids that trends.naver_shopping and trends.naver_shopping_trend take. Category 0 is the top level (12 categories, e.g. 50000000 fashion clothing, 50000002 cosmetics/beauty, 50000003 digital/appliances, 50000006 food); a category without children answers an empty list. Names are in Korean. | $0.001 | $1 |
trends.naver_shopping_trend | Daily click trend on NAVER Shopping (South Korea) for a category, or for one search keyword inside a category. Values are relative (0 to 100): 100 is the busiest day of the range, so they compare only within one answer and are not click counts. With average and peak day. Default range is the last 365 days (the maximum), from 2017-08-01. Optional visitor filters (device, gender, age decades). A category or keyword the source has no clicks for comes back with no points. | $0.001 | $1 |
trends.baidu_hot | Baidu's hot search boards (mainland China, in Chinese): what is being searched right now (realtime, up to 50 items, updated every few minutes), five topical news boards (livelihood, finance, sports, entertainment, international: 30 each) and the most searched films, TV series, novels, cars and games (10 to 30 each). Each item has its rank, a heat index (the source's own score, not a search count; comparable only within one board), a description, a new/hot badge and an up/down/same movement where the board shows them, a link and an image (the five topical boards have no image; entity boards add detail lines such as genre, cast or price). | $0.001 | $1 |
Example calls
trends.sounds ($0.005 per call): Trending sounds right now
curl -s -X POST https://whizbrew.com/v1/call/trends.sounds \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"limit":3}'
trends.prediction_markets ($0.001 per call): What people bet will happen: open prediction markets with each outcome's price (0 to 1), traded volume and pri
curl -s -X POST https://whizbrew.com/v1/call/trends.prediction_markets \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"limit":3,"query":"bitcoin"}'
trends.google_daily ($0.001 per call): Searches that are trending today in a country, with the size of the jump and the news stories behind each one
curl -s -X POST https://whizbrew.com/v1/call/trends.google_daily \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"limit":3}'
Over MCP the same call is call_tool with {"tool": "<name>", "arguments": {…}}. How often each tool works, measured from real calls: https://whizbrew.com/status.
Start
- An agent on its own: read https://whizbrew.com/agents.md. It asks for a free quote (
GET https://whizbrew.com/v1/agent/guide?goal=<the task in plain words>), then one request (POST https://whizbrew.com/v1/agent/start) gives it a key that works at once with the free credit, with no email and no sign-up form. Its human claims the account later. - A chat app (ChatGPT, Claude, Gemini): add the MCP server
https://whizbrew.com/mcpas a custom connector and sign in. No key to copy. - An agent with a shell (Claude Code, Codex, Cursor): read https://whizbrew.com/llms.txt. The agent starts a pairing with one request, its user approves with one click, and the agent holds its own key.
- Plain HTTP: create an account at https://whizbrew.com/app#signup, make a key, then
POST https://whizbrew.com/v1/call/<tool>withAuthorization: Bearer <key>.