Forendors Creator & Pricing Scraper
Pricing
Pay per event
Forendors Creator & Pricing Scraper
Extract public Forendors creator profiles, subscription prices, tiers, categories, and creator metadata. Built for creator research, pricing benchmarking, competitor monitoring, and creator economy analysis.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Kenny Ha
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
Extract public Forendors creator profiles, subscription prices, tiers, categories, and profile metadata through a fast API-backed Apify Actor. No browser automation required.
Forendors.cz is the Czech Patreon-style subscription platform for podcasters, video creators and writers. This Actor talks directly to Forendors' public API, so extracting a creator's pricing and profile data is a single call — no session handling, no HTML parsing, no browser to maintain.
A creator record looks like this (real output from a live run):
{"creatorHandle": "forendors","creatorName": "Forendors","profileUrl": "https://www.forendors.cz/forendors","isVerified": true,"postCount": 5,"categories": ["Novinky", "Tipy"],"subscriptionTiers": [{ "name": "Díky!", "price": 59, "currency": "CZK", "billingPeriod": "monthly" },{ "name": "Díky díky!", "price": 173, "currency": "CZK", "billingPeriod": "monthly" },{ "name": "Díky díky díky!", "price": 299, "currency": "CZK", "billingPeriod": "monthly" }],"lowestPrice": 59,"highestPrice": 299,"currency": "CZK","isTrending": false,"source": "handle"}
What does this Actor extract?
- Creator name, handle and profile URL
- Public bio/description
- Verification status
- Categories the creator posts under
- Subscription tiers, each with name, price, currency and billing period
- Lowest and highest public subscription price
- Total post count
- Whether the profile has a linked Discord server, RSS feed, or Spotify podcast
- Public discovery/trending status when available
Use cases
Creator research
Build structured lists of Forendors creators — profile, verification, categories and tier pricing — for research, reporting or internal databases.
Pricing benchmarking
Compare subscription pricing and tier structures across creators to see where a given price point actually sits in the market.
Competitor monitoring
Track a specific set of creators over time. Schedule repeated runs and compare datasets to see tier and pricing changes.
Agency and influencer research
Enrich creator research and outreach workflows with structured Forendors data instead of manually checking profiles one by one.
Creator economy analysis
Analyze pricing and category positioning across public Czech creator profiles.
How to use this Actor
- Add the creator handles you want under Creator handles (e.g.
chumelenice) — this is the main way to pick who gets scraped. - Optionally turn on Include trending creators to also pull in Forendors' small curated trending sample.
- Optionally set price or activity filters.
- Run the Actor. Each creator becomes one row in the dataset, ready to export as JSON, CSV or Excel.
Important: direct handles are the primary input
Forendors does not currently expose a complete public creator directory through the endpoints
this Actor uses. There is no working search endpoint and no sitemap on forendors.cz (verified by
reverse-engineering its frontend — see API-NOTES.md for the full writeup). Because of that:
- Direct handles are the recommended input. If you know which creators you care about, list
them under
handles. includeTrendingonly returns creators discoverable through Forendors' current public discovery/trending endpoints — at most about 20-25 unique creators (homepage highlights, weekly picks, most-searched). It is a small free sample, not a complete Forendors database, and this Actor does not claim otherwise.
Input
| Field | Type | Default | Description |
|---|---|---|---|
handles | array | – | Recommended. Profile URLs or bare handles to scrape. |
includeTrending | boolean | false | Also scrape Forendors' curated trending sample (~20-25 creators max, additive with handles). |
verifiedOnly | boolean | false | Only verified creators |
minTierPriceCzk | integer | – | Keep creators with at least one active tier priced at or above this |
maxTierPriceCzk | integer | – | Keep creators with at least one active tier priced at or below this |
minPostCount | integer | – | Skip creators with fewer posts than this |
hasFreeTierOnly | boolean | false | Only creators with a 0 CZK tier |
hasDiscordOnly | boolean | false | Only creators with a linked Discord server |
maxCreators | integer | 200 | 0 = no limit |
maxItems | integer | – | Hard stop on dataset rows written |
requestDelayMs | integer | 350 | Delay between API calls |
proxyConfiguration | object | off | Optional proxy |
Example 1: single creator
{ "handles": ["chumelenice"] }
Example 2: multiple creators
{ "handles": ["chumelenice", "forendors"] }
Example 3: trending creators
{ "includeTrending": true }
Example 4: handles + trending combined
{ "handles": ["chumelenice"], "includeTrending": true }
Output
One dataset row per creator (see the real example at the top of this README for the full field list). The Apify Console ships a prepared Creators table view with the most useful columns first (creator name, handle, price range, categories, trending status), and every dataset also exports to JSON, CSV, Excel, XML or HTML.
Important limitations
Forendors does not currently expose a complete public creator directory through the endpoints
used by this Actor — no working search, no sitemap, no browse-all-creators page. Direct handles
are therefore the recommended input, and includeTrending should not be treated as a complete
Forendors database; it returns only what Forendors' own public discovery/trending endpoints
currently expose (~20-25 creators).
Follower count is not included because the anonymous public API currently does not return a
reliable follower count — it always answers 0 regardless of a creator's real audience, confirmed
across multiple real profiles with visibly different follower counts on their own public pages.
Exposing that as a field would be worse than not having it at all, so this Actor leaves it out
entirely rather than publish a number that's always wrong.
No revenue or subscriber estimates. Public data can't support one — yearly-plan discounts, gift codes and the platform's own cut are all invisible from the outside, and a guess printed next to real numbers gets read as a real number.
Tier prices are whole CZK, not cents/haléře — verified against the amounts shown on live
profile pages. billingPeriod is currently always "monthly" — the API has fields for
quarterly/half-yearly/yearly pricing, but they were null on every profile tested; this Actor
does not fabricate values for them.
Pricing (pay per event)
| Event | Price | When it fires |
|---|---|---|
actor-start | $0.01 | Once per run |
creator-result | $0.004 | Per creator written to the dataset |
Charging happens before the write, so a run that hits your maxTotalChargeUsd budget stops
after delivering exactly what it charged for. A duplicate creator (e.g. requested both via
handles and returned by includeTrending) is only ever charged once. See docs/MONETIZATION.md
for worked cost examples (1 / 10 / 25 / 100 creators).
FAQ
Do I need a Forendors account? No. The Actor uses Forendors' public API only and never signs in.
Can I get every creator on Forendors?
Not through this Actor alone — there's no public directory or search on the platform (see
"Important limitations" above). Supply the handles you care about, or use includeTrending for
the small curated sample.
Why is there no follower count field?
The Forendors API itself returns 0 for anonymous requests regardless of a creator's real
audience — it's not something this Actor can see or compute, so it's left out rather than
published as a fake zero.
How fresh is the data?
Every run reads the Forendors API live. scrapedAt records the moment each row was captured.
Can I export to CSV or Excel? Yes — every Apify dataset exports to JSON, CSV, Excel, XML and HTML.
Disclaimer
This is an independent, community-built Actor and is not affiliated with, endorsed by, or sponsored by Forendors. It processes publicly accessible data only. Users are responsible for ensuring their use complies with applicable laws and Forendors' terms of service.
Development
npm installnpm run start:dev # runs against ./storage/key_value_stores/default/INPUT.jsonnpm testnpm run lintnpm run build