Apify Portfolio Expansion Planner
Pricing
Pay per event
Apify Portfolio Expansion Planner
Rank user-supplied candidate niches by public Store opportunity and textual adjacency to a user-supplied portfolio. Public Store API only for candidates, no portfolio fetching.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
Rank user-supplied candidate niches by public Store opportunity and textual adjacency to a user-supplied portfolio. Portfolio data is BYOD and never fetched from Apify. The report separates supplied portfolio context from public Store evidence and exposes bounded deterministic scores.
Pricing
Pay-per-event:
apify-actor-start: $0.005result-found: $0.15
What you get
- Candidate niches ranked by public Store opportunity and BYOD portfolio adjacency.
- Deterministic adjacency, novelty, priority, rationale, and coverage fields.
- Explicit separation between supplied portfolio text and Store-verified evidence.
- One compact dataset report plus a replay-safe
OUTPUTsummary.
How to use
- Click Try for free and provide at least one bounded portfolio actor object.
- Add candidate queries and set a unique
requestId. - Start the run and read ranked expansions from the dataset row.
Input
{"schemaVersion": "1.0","requestId": "plan-001","portfolioActors": [{"id": "a1","name": "Apify Store Idea Validator","title": "Apify Store Idea Validator","description": "Scores ideas against public Store evidence.","categories": ["MCP_SERVERS", "DEVELOPER_TOOLS"]}],"candidateQueries": ["store opportunity", "pricing benchmark"],"maxResults": 10,"freshnessMinutes": 60,"detailLevel": "compact"}
Portfolio data is validated as supplied evidence and is never fetched or treated as
Store-verified. The business envelope is written to KVS key OUTPUT; replaying the
same requestId cannot create another Dataset row or result-found charge.
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 Niche Demand Radar | Pair it in the in-house factory tooling workflow: Produce a current demand-direction snapshot for one declared niche using observed public Apify Store user... |
| 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... |
FAQ / Support
Is portfolio text fetched from an account? No. Portfolio objects are supplied by the caller and are never fetched from Apify.
What this is NOT. It is not a portfolio editor, financial forecast, or guarantee that a candidate will succeed. Report bugs through the Actor page.
Output
{"schemaVersion": "1.0","requestId": "plan-001","reportType": "portfolio_expansion_plan","generatedAt": "2026-07-31T00:00:00.000Z","sampleConfidence": "low","portfolioActorCount": 1,"expansions": [{"rank": 1,"candidate": "store opportunity","priority": 54.2,"adjacency": 40,"novelty": 60}]}