How to estimate an Apify Actor price from workload costs

Start an Actor pricing estimate with one workload, one billing unit, and the costs for that same workload. Mixing a monthly cost estimate with a price for a single run can produce a convincing-looking margin that does not describe either scenario.

The ActorConsole pricing calculator models revenue, costs, profit, margin, and a break-even price from your inputs. It is a scenario tool. The values below are illustrative USD assumptions, not current Apify fees, a market-price recommendation, or a forecast of demand.

Define the workload and billing unit

For this example, assume a workload produces 10,000 billable results. The proposed price is $5 per 1,000 results. Estimated Apify costs for that workload are $8, and other costs are $4.

Use the count of billable results for the pricing unit you are modeling. Requests, pages, records, and billable events can represent different quantities. Confirm which quantity your Actor charges for before comparing this estimate with an actual pricing configuration.

Calculate revenue, profit, and margin

The calculator uses these relationships:

Revenue = price per 1,000 × billable results ÷ 1,000
Total costs = Apify workload costs + other workload costs
Profit = revenue − total costs
Margin (%) = profit ÷ revenue × 100
Break-even price per 1,000 = total costs ÷ billable results × 1,000

For the example, revenue is $5 × 10,000 ÷ 1,000 = $50. Total modeled costs are $8 + $4 = $12. That leaves $38 of modeled profit and a 76% margin. The break-even price is $12 ÷ 10,000 × 1,000 = $1.20 per 1,000 results.

That $38 is the difference between the revenue and the costs entered in this scenario. Its usefulness depends on whether those inputs represent the workload accurately. Include relevant proxy, AI-provider, hosting, and payment costs in the other-cost estimate when they apply, and account for a cost once.

Change one assumption and compare the result

Keep the workload and $12 total cost assumption unchanged, then reduce the price to $1 per 1,000 results. Revenue becomes $10, modeled profit becomes −$2, and the margin becomes −20%. The same number of results now describes a loss in this scenario.

Next, consider a different result volume. Re-estimate the costs for that workload before comparing it with the original example. Proxy charges, retries, compute usage, and external services may change with volume; the calculator does not infer a cost curve or predict customer demand for you.

Handle empty or zero-revenue scenarios honestly

The calculator does not produce a break-even price when billable results are zero. It also leaves percentage margin undefined when revenue is zero, because dividing by zero would not give a useful percentage. Use the displayed revenue and cost values to understand that scenario instead of treating an unavailable percentage as a zero-cost result.

Review the live pricing unit before applying a change

Changing a calculator input does not change an Actor. For an owned Actor, inspect its current pricing and history, generate a pricing proposal when appropriate, and review the event names and amounts. The managed pricing write described in the pricing guide supports pay-per-event pricing, so check how the proposed events map to your modeled billing unit.

Approve only the pricing field you intend to apply, then confirm the result in pricing history. Keep the scenario separate from your actual Apify costs and creator revenue. The analytics guide and profitability guide explain where those connected-account values come from.

A practical next step

Open the pricing calculator, reproduce the example, and replace each assumption with a measured value for your own workload. Save or export the scenario if it helps your review. Before publishing a broader listing update, use the listing-audit checklist to check that the public description explains the same job and output that you priced.