Apify Store Trends API - Niche Finder, Rising Actors

Which Apify niches are rising and where is there room for a new actor? The Store only shows today's numbers. This actor answers from our own daily archive of the Apify Store: every public actor is snapshotted once a day (users in the last 7, 30 and 90 days, total users, runs, success rate, rating, price). You get rising actors, a verdict per niche keyword, and the daily history of any actor, as clean JSON.

No scraping on your side, no proxies, no login. One call, one JSON row per actor or keyword.

Who needs it

• Actor developers: find a niche with real demand and a weak top 3 before you build.
• Agencies and analysts: track which categories grow and which actors lose users.
• AI agents: ask "is there room for a new TikTok or PDF actor?" and get a verdict, not a page to parse.

Three modes

Mode	What you get
rising (default)	Actors sorted by momentum (7-day users scaled to 30 days and divided by the 30-day users, above 1 means growing faster this week), by user change, or by size. Filter by keyword, category and minimum users.
niche	One row per search term: actors in the niche, active actors, clone actors, total users, leader, top-3 share, a verdict (open, crowded, thin, contested, empty) and the top actors.
history	One row per actor: current numbers plus daily rows (users 7/30/90, total users, runs, rating, reviews, price).

How to use it (step by step)

1. Click Try for free.
2. Pick a Mode. The default (rising, minimum 10 monthly users, 50 results) works immediately.
3. For niche enter Search terms; for history enter Actors as username/name.
4. Click Start and download JSON, CSV or Excel, or call it by API.

API example (copy and paste)

Replace MY_APIFY_TOKEN with your token from Apify Console, Settings, Integrations.

curl -s -X POST "https://api.apify.com/v2/acts/martin10291~apify-store-trends-niche-finder/run-sync-get-dataset-items?token=MY_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"niche","searchTerms":["tiktok","company register","pdf"]}'

Rising actors in one category:

curl -s -X POST "https://api.apify.com/v2/acts/martin10291~apify-store-trends-niche-finder/run-sync-get-dataset-items?token=MY_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"rising","category":"AI","minUsers30":10,"sortBy":"momentum","limit":50}'

Use it from AI agents (MCP)

Add it to the Apify MCP server for Claude, Cursor or any MCP-capable agent:

https://mcp.apify.com?tools=martin10291/apify-store-trends-niche-finder

Then ask: "Which rising Apify actors in ECOMMERCE have fewer than 3 competitors?" or "Is the niche 'company register' open?". The output is flat, documented JSON.

What makes this one different

• Daily history. Other Store tools show a live snapshot. This archive keeps one snapshot per day, so you can see growth over time and ask for actor history. Our archive started on 2026-11-03 and grows every day. Past days cannot be backfilled by anyone starting later.
• Niche verdict. Not just a list: how many actors, how many are active, how many are clones, how concentrated the top 3 are, and whether the niche looks open or crowded.
• Momentum. users7 * 30 / 7 / users30. It works from day 1, because the Store itself reports 7, 30 and 90 day users.

Honest limits: history begins on 2026-11-03, so day-over-day deltas (users30Delta, users30DeltaPct) are small at first and get more meaningful each day. Every row carries comparedWith, firstSeenDay, archiveFrom and archiveSnapshots so you can see how much history stands behind the numbers. Actors that joined the archive after the comparison day are compared with their own first snapshot, so every row has a delta (comparedWith shows the day used). Data comes from public Store statistics only.

Input

Field	Default	Description
mode	rising	rising, niche or history
search	empty	Rising: keyword filter (one or more)
category	empty	Rising: Store category such as AI, ECOMMERCE, SOCIAL_MEDIA
minUsers30	10	Rising: ignore actors with fewer monthly users
sortBy	momentum	Rising: momentum, users30Delta, users30DeltaPct, users30
lookbackDays	30	Rising: compare with the snapshot about this many days ago
searchTerms	tiktok, company register, pdf (prefill)	Niche: required keywords
actors	empty	History: required, username/name
limit	50	Max rows (1 to 1000)
onlyNew	false	Rising: output only actors not output before for this Monitor ID
monitorId	default	Separate memory per watch

Output example (niche mode, shortened)

{
  "searchTerm": "tiktok",
  "actors": 438,
  "activeActors": 318,
  "cloneActors": 77,
  "users30Sum": 79522,
  "users30SumThen": 77764,
  "users30SumDeltaPct": 2.3,
  "leader": "clockworks/tiktok-scraper",
  "leaderUsers30": 33580,
  "leaderRating": 4.75,
  "leaderPriceUsd": 0.0037,
  "top3SharePct": 61.2,
  "verdict": "crowded: leader above 150 monthly users",
  "comparedWith": "2026-11-03",
  "day": "2026-11-04",
  "topActors": ["... one object per actor, same fields as rising mode ..."]
}

Rising mode row (shortened): {"actor": "corent1robert/google-play-developer-contacts", "users7": 136, "users30": 136, "users90": 140, "usersTotal": 151, "momentum": 4.29, "runs30": 774, "successRate30": 100.0, "pricingModel": "PAY_PER_EVENT", "priceUsd": 0.005, "users30Delta": 0, "comparedWith": "2026-11-03", "archiveFrom": "2026-11-03", "archiveSnapshots": 2}

Monitoring

In rising mode turn on Only new actors and set a Monitor ID. Only actors not output before for that ID are returned, for example "new actors in AI with momentum above all others since last week". The first run outputs everything. Ignored in niche and history modes.

Pricing

Pay per result: $3 per 1,000 results. One result is one dataset row (an actor in rising mode, a keyword in niche mode, an actor in history mode). A history request for an unknown actor is not saved and not charged. Failed runs (for example a server error) save nothing.

FAQ

Where does the data come from? From our own daily snapshots of the public Apify Store, kept on our server. The actor is a thin client over that archive.

How far back does it go? To 2026-11-03. See archiveFrom and archiveSnapshots in each row.

What does a verdict mean? open means a small number of active actors and a weak leader, crowded a strong leader, thin little demand, contested many similar actors, empty no actor found. It is a guide, not a guarantee; check the top actors yourself.

Why are deltas 0 right now? The archive is young. Deltas compare today with the oldest snapshot within your lookback window and grow more meaningful every day.

Does it use proxies or log in anywhere? No. It calls one API with an honest User-Agent (ApifyStoreTrends/1.0).

A run failed. Why? See the RUN_SUMMARY record in the key-value store: the lastError field says what happened (bad input, server error after 3 retries).