Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -19,17 +19,17 @@ This chapter will guide you through all the commands you need to build your firs
<Card
title="Environment variables"
desc="Learn how to provide your Actor with context that determines its behavior through a plethora of pre-defined environment variables offered by the Apify SDK."
to="/platform/actors/development/programming-interface/container-web-server"
to="/platform/actors/development/programming-interface/environment-variables"
/>
<Card
title="Status messages"
desc="Use custom status messages to inform the user about the progress of your Actor run."
to="/platform/actors/development/programming-interface/status-messages"
/>
<Card
title="Status events"
title="System events"
desc="Learn about system events sent to your Actor and how to benefit from them."
to="/platform/actors/development/programming-interface/status-messages"
to="/platform/actors/development/programming-interface/system-events"
/>
<Card
title="Container web server"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Platform usage by _FREE_ tier users is covered by Apify and does not contribute

:::

To calculate your costs for a specific run by paying user, multiply the unit cost of each service by the quantity consumed. For example, if a _BRONZE_ tier user run uses 10 compute units (CUs) at $0.2/CU, your cost would be $2.
To calculate your costs for a specific run by a paying user, multiply the unit cost of each service by the quantity consumed. For example, if a _BRONZE_ tier user run uses 10 compute units (CUs) at $0.2/CU, your cost would be $2.

If your Actor uses tiered pricing, the user's discount tier determines the unit costs applied to their runs. Your costs are lower for higher tiers, enabling you to offer more competitive pricing to these customers, while sustaining healthy profit margins.

Expand Down
5 changes: 5 additions & 0 deletions sources/platform/actors/running/store/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ All Actors in [Apify Store](https://apify.com/store) fall into one of the four p
1. [**Pay per event**](#pay-per-event) - you pay for specific events the Actor creator defines, such as generating a single result or starting the Actor. Most Actors include platform usage in the price, but some may charge it separately - check the Actor's pricing for details.
1. [**Pay per usage**](#pay-per-usage) - you only pay for the platform resources (compute units, data transfer, etc.) the
Actor consumes. There are no additional charges from the Actor developer.
1. [**Pay per result**](#pay-per-result) - you pay a fixed price for every 1,000 results the Actor produces, typically items stored in the run's default dataset. Platform usage is included in this price.
1. [**Rental**](#rental-actors) - to continue using the Actor after the trial period, you must rent the Actor from the developer and pay a flat monthly fee in addition to the costs associated with the platform usage that the Actor generates.

:::note Post-run storage costs
Expand Down Expand Up @@ -71,6 +72,10 @@ _For more information on platform usage cost see the [usage and resources](../us

:::

### Pay per result

With pay per result pricing, you pay a fixed price for every 1,000 results an Actor run produces - typically items stored in the run's default dataset. Platform usage is included in this price, so you are not charged for it separately. When starting a run, you can cap the number of results to keep your costs under control.

### Rental Actors

<RentalSunset/>
Expand Down
Loading