How to monetize Apify Actors
Publishing on the Apify Store lets other people run your scrapers and automations while you earn revenue. This page explains pricing models, Apify’s commission, payout mechanics, and a practical publish checklist.
You can monetize Apify Actors by setting pay-per-result, pay-per-event, or rental pricing. Apify takes a commission, and you receive payouts via bank transfer or PayPal.
Why developers publish paid Actors
Apify combines hosting, scheduling, proxy options, and billing so buyers can run your Dockerized Actor without cloning your repo. When your tool solves a painful, high-frequency problem (maps leads, e-commerce monitoring, social exports), Store distribution can become recurring income.
Pricing models (what each means)
| Model | What buyers pay for | When to use it |
|---|---|---|
| Pay per event (PPE) | A defined event (e.g., one export, one profile, one search page) | Flagship model for new monetization. Aligns price with measurable value, gets priority Store placement, and is fully compatible with AI/MCP usage. official docs |
| Pay per result (PPR) | Each result row or item returned | Bills per output row. Per-result billing is also available as an event inside PPE, so new Actors increasingly express it through PPE. official docs |
| Pay per usage | Platform compute only (no markup), via the rental-style flat or usage path | Simple option when your value scales directly with compute. The buyer runs the Actor with no charge beyond platform usage. |
| Rental | Flat monthly fee for access during the term | Being sunset: no new rentals from April 1, 2026 and full retirement on October 1, 2026. Do not build new listings on it. rental docs |
| Free | $0 to run (buyer still pays platform compute) | Great for adoption, lead-gen to services, or upselling a premium Actor |
Plan new monetization around pay per event, the flagship model. Rental is being retired: Apify stops accepting new rental listings on April 1, 2026 and fully retires the model on October 1, 2026 (rental docs). Pay per result and pay per usage remain available; many builders now express per-result billing through a PPE event for priority placement.
Commission structure
Apify operates as a marketplace: when someone pays for your commercial pricing, you earn a revenue share and Apify retains a platform commission for payment processing, distribution, and infrastructure.
- Developers commonly receive 80% of eligible Actor revenue under the Store terms. Treat the remainder as Apify’s commission slice.
- Your net payout also reflects refunds, chargebacks, and any periods where infrastructure spend on your Actor exceeds earned revenue (negative profit can reduce a monthly payout).
Always read the latest Store terms and monetize docs, because percentages and policies can change.
Payout mechanics
Typical rhythm (confirm dates in Console emails):
| Step | Detail |
|---|---|
| Invoice generation | Around the 11th of the month |
| Review window | About three business days of reconciliation |
| Minimum payout | $100 for bank transfer, $20 for PayPal (thresholds subject to change; verify in Console) |
| Negative profit | If your Actor runs at a loss for the period, it may offset amounts owed to you |
How to set up pricing in Console
Exact UI labels move over time, but the workflow is stable:
- Open your Actor in Apify Console.
- Navigate to Monetization / Pricing (terminology may read Publishing → Monetize).
- Choose Free, Pay per event, Pay per result, or Pay per usage (rental is being sunset, so new listings should pick another model).
- Set prices, free tiers (if offered), and documentation that explains what counts as an event or result.
- Save and complete any Store listing requirements (README, categories, images).
Apify’s canonical references: Monetize overview and Pricing and costs.
Step-by-step: ship a paid Actor buyers trust
You already saw the structured HowTo JSON-LD above; here is the same path with engineering detail.
1) Prove reliability before you monetize
- Validate all inputs and fail with actionable errors.
- Add retries, timeouts, and proxy configuration where targets need it.
- Log enough for you to debug user issues without their secrets.
// Pattern: validate input early in a monetized Actor
import { Actor } from 'apify';
await Actor.init();
const input = await Actor.getInput();
if (!input?.startUrls?.length) {
throw new Error('Provide at least one start URL in startUrls.');
}
// ... crawler or browser automation ...
await Actor.exit();
2) Write documentation that sells and defends you
Include:
- What the Actor does in one paragraph (no buzzwords).
- Input table with types, defaults, and limits.
- Output schema with example JSON.
- Cost guidance (“typical run = N events × price + platform CU”).
- Known limitations (login walls, geo blocks, rate limits).
3) Publish a versioned build
Use the Apify CLI or Console to push Docker builds. Buyers pin versions; breaking changes require communication and migration notes.
4) Choose pricing that matches compute
If each successful row costs you proxy + browser time, set PPE so median runs remain profitable after Apify’s commission and your support burden.
5) Respond after launch
- Watch issues, reviews, and failure rates.
- Pricing changes may require notice periods and frequency limits, so check current Store policy (often 14-day notice, once per month).
Creator plan for builders
Apify’s Creator plan is $1/month plus pay-as-you-go, with a one-time $500 prepaid usage bonus usable in the first 6 months. It is aimed at community developers building and publishing their own Actors, so it is useful while you harden an Actor before charging others (pricing).
Revenue habits that compound
- Portfolio: related Actors cross-sell (maps scraper + enrichment Actor).
- Integrations: document webhooks, API, and Make/n8n paths, because automation buyers love easy pipes.
- SEO inside the Store: specific titles (“LinkedIn jobs scraper”) beat vague ones (“data tool”).
- Maintenance: stale Actors lose rank; schedule weekly smoke tests on canonical URLs.
FAQ
Income varies with niche demand, pricing, reliability, and reviews. Some developers treat it as side income; top-maintained Actors in high-intent categories can reach meaningful monthly revenue. There is no guaranteed floor.
Pay per event bills defined actions you specify in the pricing model, which aligns price with value and is now the flagship model. Pay per result bills per output row and is still available; on the platform per-result billing can also be expressed as an event inside a pay-per-event model, which earns priority Store placement.
Apify keeps a marketplace fee on commercial usage; developers typically receive the majority share (commonly cited as 80% under Store terms). Read the latest Store terms for authoritative numbers.
Monthly invoicing cycles around the 11th with a short review window. You must exceed minimum payout thresholds (commonly $100 for bank transfer and $20 for PayPal) before funds move.
Yes. Sites change selectors, introduce bot defenses, and break parsers. Fast fixes protect your rating and refund rate.
Many authors launch free to gather reviews, then introduce pay per event once reliability is proven. Communicate changes per Store policy.
Sources
Verified against Apify documentation and policies as of May 2026:
Common mistakes and fixes
Pay-per-event pricing confuses buyers.
Document one worked example: typical input, expected events, and estimated cost. Link to Apify’s pricing UI strings in your README so users can reproduce the math.
Payout is lower than expected.
Remember Apify’s platform commission on charged usage, refunds/chargebacks, and negative profit if your Actor’s infra costs exceed revenue in a period. Review the monthly statement in Console.
Store review keeps rejecting the listing.
Tighten input validation, add screenshots or sample datasets, disclose limitations (geo, login, CAPTCHA), and prove stable success rate on example URLs.
