Graphtreon Patreon Creator Earnings Scraper
Graphtreon Patreon Creator Earnings Scraper
Scrape estimated Patreon creator earnings, patron counts, and ranking data from Graphtreon — the only publicly available source that reverse-engineers Patreon income by analyzing tier and patron count data.
What you get
For each Patreon creator, the actor returns:
| Field | Description |
|---|---|
patreon_creator_name |
Creator display name |
patreon_url |
Direct Patreon page URL |
graphtreon_url |
Graphtreon stats page URL |
category |
Patreon category slug (e.g. video, gaming, music) |
paid_member_count |
Number of paying patrons |
estimated_monthly_earnings_min_usd |
Lower bound of monthly earnings estimate (USD) |
estimated_monthly_earnings_max_usd |
Upper bound of monthly earnings estimate (USD) |
earnings_rank_overall |
Overall earnings rank across all Patreon creators |
earnings_rank_in_category |
Earnings rank within the creator's category |
launch_date |
ISO 8601 date the Patreon page launched |
scraped_at |
ISO 8601 timestamp of the scrape |
Around 250,000 creators are indexed in Graphtreon. Earnings estimates are null for creators who opt out of the feature.
Why Graphtreon
Patreon itself does not expose creator earnings — it only shows patron counts at the tier level, not the dollar amounts. Graphtreon back-computes earnings estimates from public tier pricing and patron count data, making it the canonical data source for:
- Creator-economy market analysis
- Influencer pricing benchmarks
- VC and brand research
- Journalism and industry reports
How to use
Set maxItems to limit the number of records. Set to 0 or leave empty to scrape all ~250k creators.
{
"maxItems": 1000
}
The actor walks Graphtreon's sitemap (12 child sitemaps, each listing ~20k creator URLs), fetches each creator's detail page, and extracts all available data via the server-rendered HTML.
Proxy note
Graphtreon blocks datacenter IP ranges via Cloudflare IP reputation filtering. The actor automatically routes requests through Apify Residential proxies — no additional configuration needed.
Performance
- Default memory: 1024 MB
- Default timeout: 4 hours
- Concurrency: 5 parallel requests
- Full dataset (250k creators): runs in approximately 12-16 hours on default settings
Reduce maxItems for faster runs focused on the highest-ranked creators.