docs: Update info on pricing model selection (#2629)

Closes [#28360](apify/apify-core#28360).

Author: szaganek

sources/platform/actors/publishing/images/apify-actor-start.png

@@ -1,6 +1,6 @@
 ---
 title: Monetize your Actor
-description: Monetize your Actors on Apify Store by choosing a pricing model such as pay per event or a flat monthly rental fee for users.
+description: Monetize your Actors on Apify Store and earn regular passive income.
 slug: /actors/publishing/monetize
 sidebar_position: 2.5
 ---
@@ -9,48 +9,39 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import RentalSunset from '../../../../_partials/_rental-sunsetting.mdx';
 
-Apify Store allows you to monetize your web scraping, automation, and AI agent projects by publishing them as paid Actors. This guide explains the available pricing models and how to get started.
+Apify Store allows you to monetize your web scraping, automation, and AI agent projects by publishing them as paid Actors.
 
 ## Pricing models
 
-Actors in Apify Store can be published under one of the following pricing models:
+You can publish Actors on Apify Store under one of the following pricing models:
 
-- _Pay per event (PPE)_: Users pay for specific events that are programmatically triggered from the Actor's source code. These events are defined by the developer and can include actions such as generating a single result or starting an Actor. The developer also chooses whether to pass the platform usage costs to users.
-- _Pay per usage_: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor.
-- _Rental_: Users pay for the platform usage costs. However, after a trial period, they need to pay a flat monthly fee to the developer to continue using the Actor.
-
-    <RentalSunset/>
+- [Pay per event (PPE)](/platform/actors/publishing/monetize/pay-per-event): Users pay for specific events that are programmatically triggered from the Actor's source code. You can define these events and include actions such as generating a single result or starting an Actor. You can also choose whether to pass the platform usage costs on to users.
+- Pay per usage: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor.
 
 For a detailed comparison of pricing models from the perspective of your users, see [Actors in Store](/platform/actors/running/actors-in-store).
 
-## Key benefits
-
-The following table compares the two main pricing models available for monetizing your Actors:
-
-| Feature/Category         | Pay-per-event (PPE)                                              | Rental                         |
-|--------------------------|------------------------------------------------------------------|--------------------------------|
-| Revenue scalability      | Unlimited, scales with usage                                     | Capped at monthly fee          |
-| AI/MCP compatibility     | ✅ Fully compatible                                              | ❌ Not compatible              |
-| User cost predictability | Predictable                                                      | Unpredictable (rental + usage) |
-| Store discounts          | ✅ Store discounts available                                     | ❌ Single price only           |
-| Marketing boost          | Priority store placement                                         | Standard visibility            |
-| Commission opportunities | Standard 20%                                                     | Standard 20%                   |
-| Custom event billing     | ✅ Charge for any event                                          | Not available                  |
-| Per-result billing       | Optional (via event; automatic via `apify-default-dataset-item`) | Not available                  |
-
 ## Set up monetization
 
-To monetize your Actor:
+To set up monetization for your Actor, first complete your billing and payment details. Then, you can define the pricing for your Actor:
 
 1. Log in to [Apify Console](https://console.apify.com).
 1. In the left-side panel, go to **Development** > **My Actors**.
 1. From the table, select the Actor you want to monetize.
 1. Go to the **Publication** tab.
-1. Complete each section with required information.
-    - In **Monetization** section, complete your billing and payment details, and choose your [pricing model](#pricing-models).
-1. Select **Publish on Store**.
+1. In **Monetization** section, select **Set up monetization**.
+
+The monetization setup consists of three steps:
+
+1. In the **Actor pricing** step, you can:
+    - Modify or delete the [`apify-actor-start`](/platform/actors/publishing/monetize/pay-per-event#synthetic-start-event) event.
+    - Modify or delete the [`apify-default-dataset-item`](/platform/actors/publishing/monetize/pay-per-event#synthetic-default-dataset-item-event) event.
+    - Define [custom events](/platform/actors/publishing/monetize/pay-per-event#actor-events) and their prices.
+    - [Transfer the platform usage costs on to users](/platform/actors/publishing/monetize/pay-per-event#platform-usage-costs).
+    - Set the minimal cost that users can choose as max cost per run.
+1. In the **Primary event** step, select the event that best represents the main value of your Actor. By default, the dataset event or the only existing event is used.
+1. In the **Review** step, verify the final pricing for your Actor before confirming.
 
-![Monetization section](../images/monetization.svg)
+![Publication tab in Apify Console](../images/monetization.svg)
 
 ### Change monetization
 

sources/platform/actors/publishing/images/pay_per_event_and_usage_toggle.png

@@ -8,11 +8,24 @@ sidebar_position: 1
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-The PPE pricing model offers a flexible monetization option for Actors on Apify Store as it allows you to charge users based on specific events triggered programmatically by your Actor's code.
+The pay per event (PPE) pricing model offers a flexible monetization option for Actors on Apify Store:
 
-PPE lets you define pricing for individual events. You can charge for specific events directly from your Actor using the [JS](/sdk/js/reference/class/Actor#charge)/[Python](/sdk/python/reference/class/Actor#charge) SDK, or by calling the [PPE charging API](/api/v2/post-charge-run) directly. Common events include Actor start, dataset item creation, and external API calls.
+- You can charge users based on specific events triggered programmatically by your Actor's code. Common events include starting an Actor, creating a dataset item, or calling an external API.
+- You can define different pricing for individual events.
+- You can charge for specific events directly from your Actor using the [JS](/sdk/js/reference/class/Actor#charge) or [Python](/sdk/python/reference/class/Actor#charge) SDK, or by calling the [PPE charging API](/api/v2/post-charge-run) directly.
 
-The details on how your cost is computed can be found in [Example of a PPE pricing](#example-of-a-ppe-pricing).
+See the key benefits of the PPE pricing model:
+
+| Category | Pay per event (PPE) |
+| --- | --- |
+| Revenue scalability | Unlimited, scales with usage |
+| AI/MCP compatibility | ✅ Fully compatible |
+| User cost predictability | Predictable |
+| Store discounts | ✅ Store discounts available |
+| Marketing boost | Priority store placement |
+| Commission opportunities | Standard 20% |
+| Custom event billing | ✅ Charge for any event |
+| Per-result billing | Optional (via event; automatic via `apify-default-dataset-item`) |
 
 :::tip Additional benefits
 
@@ -54,21 +67,19 @@ An Actor's negative net profit does not affect the positive profit of another Ac
 1. _Test your pricing_: Run your Actor and analyze cost-effectiveness using a special dataset.
 1. _Communicate value_: Ensure pricing reflects the value provided and is competitive.
 
-## Pass platform usage to users
+## Pass platform usage costs on to users {#platform-usage-costs}
 
-During initial development or when testing pricing strategies, you can pass the platform usage costs directly to users to avoid negative profit margins. Users then pay for both the defined events and the underlying platform usage. Use this approach temporarily until you determine accurate event prices.
+To avoid negative profit margins during initial development or when testing pricing strategies, you can pass the platform usage costs on to users. As a result, users pay for both the defined events and the underlying platform usage.
 
 :::caution Reduced pricing transparency
 
-Charging platform usage separately is less transparent for users and may discourage them from using your Actor. This also negatively impacts your [**Actor quality score**](../quality-score). Turn off this option once you determine accurate event prices.
+Charging platform usage separately is less transparent for users and may discourage them from using your Actor. It also negatively impacts your [**Actor quality score**](../quality-score). Use this approach only until you determine accurate event prices.
 
 :::
 
-Use the **Pay per event + usage** toggle to enable or disable this option in the monetization flow.
-
-![Pay per event with usage toggle button](../images/pay_per_event_and_usage_toggle.png)
+To pass platform usage costs on to users, in the **Actor pricing** step of the [monetization setup](/platform/actors/publishing/monetize#set-up-monetization), switch on the **Pay per event + usage** toggle.
 
-The option can be turned off at any time with immediate effect, as it is a positive change for the user. Turning it on will take 14 days.
+Turning this option on takes 14 days to take effect. However, you can turn it off immediately, as it is a positive change for users.
 
 ## Respect user spending limits
 
@@ -148,11 +159,11 @@ When using [Crawlee](https://crawlee.dev/), use `crawler.autoscaledPool.abort()`
 
 Use the [Apify SDKs](/sdk) (JS or Python) or the [`apify actor charge`](/cli/docs/next/reference#apify-actor-charge-eventname) when using the Apify CLI to simplify PPE implementation into your Actor. SDKs help you handle pricing, usage tracking, idempotency keys, API errors, and, event charging via an API. You can also choose not to use it, but then you must handle API integration and possible edge cases manually.
 
-### Use synthetic start event `apify-actor-start`
+### Use synthetic start event `apify-actor-start` {#synthetic-start-event}
 
 :::info Synthetic Actor start event recommended
 
-We recommend using the synthetic Actor start event in PPE Actors. It benefits both you and your users.
+Apify recommends using the synthetic Actor start event in all Actors. It benefits both you and your users.
 
 :::
 
@@ -177,23 +188,23 @@ The default price of the event is set intentionally low. This pricing means that
 - You can increase the price of the event if you wish, but you _won't get more free compute_.
 - You can delete the event if you wish, but if you do, you will _lose the free 5 seconds_ of compute.
 
-#### Synthetic start event for new Actors
-
-For new Actors, this event is added automatically as you can see on the following screen:
+#### Synthetic start event for new and existing Actors
 
-![New Actor - synthetic start event](../images/apify-actor-start.png)
+For new Actors, the `apify-actor-start` event is added automatically.
 
-#### Synthetic start event for existing Actors
+For existing Actors, you can add this event manually:
 
-If you have existing Actors, you can add this event manually in Apify Console in the **Publication** tab.
+1. Access your Actor's [monetization setup](/platform/actors/publishing/monetize#set-up-monetization).
+1. In the **Actor pricing** step, under **Event name**, add `apify-actor-start`.
+1. Complete the remaining event details: title, description, and price.
 
 #### Synthetic start event for Actors with start event
 
 Your Actor might already have a start event defined, such as `actor-start` or another variant of the event name. In this case, you can choose whether to use the synthetic start event or keep the existing start event.
 
 If you want to use the synthetic start event, remove the existing start event from your Actor and add the synthetic start event in Apify Console in the **Publication** tab.
 
-### Use synthetic default dataset item event `apify-default-dataset-item`
+### Use synthetic default dataset item event `apify-default-dataset-item` {#synthetic-default-dataset-item-event}
 
 The `apify-default-dataset-item` synthetic event charges users for each item written to the run's default dataset. It lets you align PPE pricing with per-result use cases without adding charging code to your Actor.
 
@@ -312,7 +323,7 @@ async def main():
 
 Try to limit the number of events. Fewer events make it easier for users to understand your pricing and predict their costs.
 
-### Make events produce visible results
+### Make events produce visible results {#actor-events}
 
 For Actors that produce data, events should map to something concrete in the user's dataset or storage.