Apify Niche Demand Radar
Pricing
Pay per event
Apify Niche Demand Radar
Produce a current demand-direction snapshot for one declared niche using observed public Apify Store user metrics. Public Store API only, no LLM.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Produce a current demand-direction snapshot for one declared niche using observed
public Apify Store user metrics. The Actor uses only GET https://api.apify.com/v2/store.
It labels observed movement with explicit comparison windows and keeps missing evidence visible.
Pricing
Pay-per-event:
apify-actor-start: $0.005result-found: $0.05
What you get
- A current Store cohort and observed user-metric comparison.
- A deterministic acceleration score and trajectory classification.
- Explicit coverage and confidence when fields are missing.
- One compact dataset report plus a replay-safe
OUTPUTsummary.
How to use
- Click Try for free and enter a niche with one or more keywords.
- Choose
7d_vs_30dor30d_vs_90dand set a uniquerequestId. - Start the run and read the trajectory and evidence from the dataset row.
Input
{"schemaVersion": "1.0","requestId": "radar-001","niche": "store analytics","keywords": ["store", "analytics"],"comparisonWindow": "7d_vs_30d","maxResults": 10,"freshnessMinutes": 60,"detailLevel": "compact"}
Related tools
Related tools for adjacent workflows in in-house factory tooling.
| Actor | What it does |
|---|---|
| Apify Market Gap Finder | Pair it in the in-house factory tooling workflow: Compare user-declared niches against the public Apify Store and rank evidence-backed market gaps |
| Apify Pricing Benchmark Advisor | Pair it in the in-house factory tooling workflow: Summarize visible public Apify Store event-price distributions for a declared cohort |
| Apify Actor Idea Validator | Pair it in the in-house factory tooling workflow: Assess one proposed Apify Actor idea against public Store similarity, activity, quality, competition and... |
| Apify Portfolio Expansion Planner | Pair it in the in-house factory tooling workflow: Rank user-supplied candidate niches by public Store opportunity and textual adjacency to a user-supplied... |
FAQ / Support
Is trajectory a forecast? No. It is a deterministic label over observed 7, 30, or 90-day Store metrics.
What this is NOT. It is not continuous monitoring, an alerting service, or a revenue estimate. Report bugs through the Actor page.
The business envelope is written to KVS key OUTPUT; the same requestId is a
replay and cannot create another Dataset row or result-found charge.
Output
{"schemaVersion": "1.0","requestId": "radar-001","reportType": "niche_demand_snapshot","generatedAt": "2026-07-31T00:00:00.000Z","sampleConfidence": "low","niche": "store analytics","comparisonWindow": "7d_vs_30d","trajectory": "steady","opportunity": { "score": 54.3 }}