Whop Content Rewards Scraper - Clipping Campaign Finder

Get every Whop Content Rewards campaign as clean structured data in one run: reward per 1,000 views, total budget, budget already spent, budget left, progress %, accepted platforms, campaign type, category, creator count and status.

Then - and this is the part no other Whop scraper does - the Actor tells you how fast each campaign is actually paying out, computed from that single run: daily burn rate, days of budget left, average payout per creator, and a 0-100 opportunity score.

Stop scrolling the discover feed and screenshotting campaign cards. One run = the full directory (`400-500 campaigns), filterable, scored and sorted - ready for spreadsheets, dashboards, alerts, or your AI agent.

Who is this for?

• Clippers & clipping agencies - find the best-paying campaigns before they saturate. Sort by opportunity score, filter by payout-per-creator, cap the competition with max creators.
• Creators & brands running campaigns - benchmark your reward rate, budget and burn rate against every other live campaign in your category.
• Analysts & builders - the creator-economy "gig board" as a dataset: track new campaign launches, budget burn-rates and platform trends over time.
• AI agents (MCP) - pay-per-event Actors are callable as tools by AI agents. "Find me active gaming clipping campaigns paying at least $2/1K with at least $10K budget left and under 300 creators" becomes a single tool call.

What makes this Actor different

Burn-rate intelligence from your first run, not your second.

Other Whop scrapers can tell you what changed between two runs - which means run 1 teaches you nothing. This Actor derives payout velocity from data the site already publishes, so the very first run answers the question that actually matters:

Question a clipper asks	Field that answers it
Is this campaign actually paying, or just advertising a big budget?	dailyBurnUsd - USD paid out per day since funding
Will the money still be there when my clip gains traction?	estimatedDaysLeft - runway at the current burn rate
What did an average clipper here actually earn?	payoutPerCreatorUsd - budget spent divided by creators
Can I realistically compete with the people already in?	viewsPerCreator, creators
Is the budget actually moving, or just posted?	budgetPace, dailyBurnUsd
How many more views will this campaign pay for at all?	estimatedViewsRemaining
Just tell me what to clip tonight.	opportunityScore - 0-100, sortable

No snapshot, no state, no second run, no extra charge.

Output (one item per campaign)

Field	Example	Notes
title	Call of Duty MW4 - DMZ Clipping
brand	Call of Duty
opportunityScore	63.4	0-100 composite - see scoring below
rewardPerThousandViews	1.5	USD per 1,000 views
totalBudgetUsd	40000
budgetSpentUsd	4447
budgetLeftUsd	35553	computed - the "is it still worth posting" signal
dailyBurnUsd	4000	USD/day paid out since funding
estimatedDaysLeft	52.5	runway at the current burn rate - uncapped, so a huge number means "stalled"
budgetPace	healthy	that runway as a bucket: draining / healthy / slow / stalled
payoutPerCreatorUsd	12.5	what an average creator has earned so far
viewsPerCreator	7250	competition/feasibility signal
estimatedViewsRemaining	140000000	views the leftover budget can still pay for
progressPercentage	11	% of budget consumed
ageDays	10	days since funding
status	active	or ended with status: "all" input
campaignType	clipping	clipping / ugc
category	Gaming
platforms	["tiktok","instagram","youtube"]
creators	845	competition signal
successRatePct, totalViews, engagement	82, 2900000, 12.1	campaign stats
fundedAt	2026-06-01T12:00:00.000Z	spot fresh campaigns
campaignUrl	https://whop.com/mw4-dmz-clipping/	jump straight to the campaign
description	full rules text	hook/format/whitelist requirements
raw	original strings	exact values as displayed on the site

Any field the site does not publish for a given campaign comes back null - never a fabricated zero.

How the opportunity score works

Deliberately simple, documented, and reproducible so you can argue with it:

• 35% reward rate - $/1K views, saturating at $5/1K
• 25% budget headroom - budget left, saturating at $25,000
• 25% low competition - decays as creators pile in (100 creators = half marks). Capped at half marks while a campaign has never paid anyone: an empty board that has paid $0 is untested, not uncontested, and the data cannot tell those apart
• 15% payout velocity - full marks for 3-60 days of runway; penalised both when a campaign drains within a day and when it is effectively stalled (a big budget nobody is being paid from is not an opportunity)

Campaigns with no reward rate or no budget data score null rather than a misleading number.

Unproven campaigns are not hidden - a fresh board with a good rate and real budget is a genuine opportunity, and it still ranks. It just doesn't outrank a campaign that is provably paying out. On the live board (12 Aug 2026) this moved campaigns that had paid $0 from 10 of the top 15 slots down to 4.

Input highlights

• status - active (default) or all
• minRewardPerThousand, minBudgetLeftUsd, maxProgressPercentage - the classic three
• maxCreators - cap the competition (e.g. 200 = campaigns clippers have not found yet)
• minPayoutPerCreatorUsd - only campaigns with proof of payout (e.g. 5)
• minEstimatedDaysLeft - skip campaigns that will drain before your clip lands
• minOpportunityScore - one number instead of five filters
• platforms, campaignTypes, categories, searchText - slice the directory
• sortBy - budgetLeft (default), opportunity, reward, payoutPerCreator, burn, daysLeft, fewestCreators, newest, progress
• maxItems - you are only charged for returned results

Example: the low-competition, proven-payer query

{
  "status": "active",
  "minRewardPerThousand": 2,
  "minPayoutPerCreatorUsd": 5,
  "maxCreators": 300,
  "minEstimatedDaysLeft": 3,
  "sortBy": "opportunity",
  "maxItems": 25
}

Campaigns paying at least $2/1K, that have already paid an average creator $5+, with fewer than 300 people in, and at least 3 days of budget runway - ranked best first.

How to schedule this Actor (recommended setup)

Campaign boards rot fast: budgets drain, new campaigns launch daily, and the good ones saturate within hours. A scheduled run is how you get there first.

1. Run the Actor once with the input you want and check the results.
2. On the Actor page open the ... menu and choose Schedule Actor (or go to Schedules and click Create new).
3. Set the cron expression:
   • 0 */6 * * * - every 6 hours. Good default for most clippers.
   • 0 * * * * - hourly. Use when you are competing for fresh, high-CPM campaigns.
   • 0 7 * * * - once every morning. Cheapest useful cadence.
4. Attach the saved input. A tight input (maxItems: 25, sortBy: "opportunity") keeps every scheduled run to a few cents.
5. Add an integration so you do not have to check manually: Integrations, then Slack / Webhook / Google Sheets / Zapier / Make, triggered on Run succeeded. Your feed of fresh, ranked campaigns arrives on its own.

Catching launches: combine sortBy: "newest" with maxItems: 20 on an hourly schedule - new campaigns surface at the top before the creator count climbs. Add maxCreators: 100 and every item that lands in your inbox is a campaign nobody has piled into yet.

Why this Actor

• HTTP-only, no browser - fast (seconds, not minutes) and cheap to run.
• Defensive parser - tolerates site structure drift; failures degrade gracefully instead of crashing mid-run.
• Pay per event - tiny flat start fee plus a per-campaign fee. A typical "active campaigns" run costs well under a dollar. Filtered runs cost cents.
• No free-plan cap. Free-plan users get the same full directory as everyone else - the Actor does not throttle results by plan.

FAQ

Is this legal? The Actor only reads the public campaign directory - the same data anyone sees in a browser without logging in. No login, no private data, no bypassing access controls. Review the Whop terms for your specific use case.

How fresh is the data? Each run fetches the live directory at that moment. See the scheduling section above for a hands-off setup.

Do I need a second run for the burn-rate fields? No. That is the point - dailyBurnUsd, estimatedDaysLeft and payoutPerCreatorUsd are all derived from a single run.

Why is estimatedDaysLeft sometimes in the thousands? Because it is real. The budget is barely moving, which means almost nobody is being paid - budgetPace calls that stalled, and opportunityScore penalises it just as hard as a campaign that drains tonight. Earlier versions clamped this at 999; that hid the difference between a stalled board and a genuine long runway, so the cap is gone.

Why is estimatedDaysLeft null on some campaigns? Nothing has been paid out yet, so the burn rate is genuinely unknown. We report null instead of pretending the runway is infinite.

A field came back null? Some campaigns genuinely omit fields (e.g. UGC campaigns without a per-view rate). Original display strings are always preserved under raw.

Found a bug, or want another field? Open a ticket on the Issues tab.

Changelog

• 0.2.2 - Data-quality fixes found by auditing all 456 live campaigns. Ranking fix: a campaign that has never paid anyone no longer collects near-full marks for "low competition" - untested is not uncontested - which moved campaigns that had paid $0 from 10 of the top 15 slots down to 4. estimatedDaysLeft is no longer clamped at 999 (that magic number affected 12% of rows and silently broke minEstimatedDaysLeft filtering); new budgetPace bucket (draining / healthy / slow / stalled); viewsPerCreator keeps two decimals below 10 so a brand-new campaign no longer renders as a flat 0. No price change.
• 0.2.1 - Two output views in the Console/Store Output tab: Overview and Payout speed (burn rate, runway, $/creator side by side). Full Actor output schema added, so AI agents and the API can discover the result shape automatically. No price change.
• 0.2 - Single-run burn-rate intelligence: dailyBurnUsd, estimatedDaysLeft, payoutPerCreatorUsd, viewsPerCreator, estimatedViewsRemaining, ageDays, opportunityScore. Four new filters and five new sort orders. Typed output schema added. No price change.
• 0.1 - Initial release: full Content Rewards directory, HTTP-only, pay-per-event.

Was this Actor useful?

If it saved you an afternoon of scrolling the discover feed, a short review on the Store page helps other clippers decide whether to try it. Reviews are the only signal buyers have before they spend anything.

If something is wrong instead, please open a ticket on the Issues tab rather than leaving it broken - field requests and parser bugs get fixed.