apify · mtrunkat · Jul 3, 2026 · Jul 3, 2026 · szaganek · Jul 3, 2026
diff --git a/sources/platform/actors/publishing/actor-rating.mdx b/sources/platform/actors/publishing/actor-rating.mdx
@@ -31,7 +31,7 @@ To respond, on a user's review, select **Options** > **Reply**.
 
 ### Edit your reply
 
-To edit your response, on your reply, select **Options** > **Edit**.
+To edit your response, on the review, select **Options** > **Edit reply**.
 
 ## Report a review
 

diff --git a/sources/platform/actors/publishing/actor-status.mdx b/sources/platform/actors/publishing/actor-status.mdx
@@ -49,4 +49,4 @@ To let your users know that the Actor is no longer being developed, use the **De
 
 Don't delete the Actor as it might break the existing integrations.
 
-Note that the deprecated Actors aren't searchable in Apify Store. The **Deprecated** status is also automatically set when your Actor fails the [automated testing](../development/automated_tests.md) process for 30 days.
+Note that the deprecated Actors aren't searchable in Apify Store. The **Deprecated** status can also be set automatically if your Actor keeps failing the [automated testing](../development/automated_tests.md) process. In that case, the Actor is first placed **Under maintenance** after about 3 days, receives a deprecation warning 14 days later, and is set to **Deprecated** after another 14 days if it remains unfixed.
diff --git a/sources/platform/actors/publishing/index.mdx b/sources/platform/actors/publishing/index.mdx
@@ -5,6 +5,8 @@ sidebar_position: 7.5
 slug: /actors/publishing
 ---
 
+import RentalSunset from '../../../_partials/_rental-sunsetting.mdx';
+
 > Sharing is caring but you can also make money from your Actors. Check out the [blog post](https://blog.apify.com/make-regular-passive-income-developing-web-automation-actors-b0392278d085/) for more context.
 
 ## Publish process
@@ -33,7 +35,9 @@ Publishing your Actor on Apify Store transforms your code, eliminating tradition
 Packaging your software as an Actor allows you to launch new SaaS product faster and earn income through various monetization models that match your Actor's value proposition like:
 
 - Pay-per-event for specific operations
-- Fixed rental fee for continuous access
+- Pay-per-usage based on platform resource consumption
+
+<RentalSunset />
 
 To learn more, visit the [Actors in Store](/platform/actors/running/actors-in-store#pricing-models) page.
 

diff --git a/sources/platform/actors/publishing/monetize/index.mdx b/sources/platform/actors/publishing/monetize/index.mdx
@@ -86,11 +86,11 @@ If your PPE Actor's price doesn't cover its monthly platform usage costs, it wil
 
 :::
 
-You have 3 days to review your payout invoice in the **Development >Insights > Payout** section. During this period, you can either approve the invoice or request a revision, which we will process promptly.
+You have 3 days to review your payout invoice in the **Development > Insights > Payout** section. During this period, you can either approve the invoice or request a revision, which we will process promptly.
 If no action is taken, the payout will be automatically approved on the 14th, with funds disbursed shortly after. Payouts require meeting minimum thresholds of either:
 
-- $20 for PayPal
-- $100 for other payout methods
+- $20 for PayPal and Wise
+- $100 for other payout methods (bank accounts)
 
 If the monthly profit does not meet these thresholds, as per the [Terms & Conditions](/legal/store-publishing-terms-and-conditions), the funds will roll over to the next month until the threshold is reached.
 
@@ -104,9 +104,9 @@ When monetizing your Actor, you might want to limit features or usage for users
 
 ## Actor analytics
 
-Monitor your Actors' performance through the [Actor Analytics](https://console.apify.com/actors/insights/analytics) dashboard under **Development > Insights > Analytics**.
+Monitor your Actors' performance through the [Insights](https://console.apify.com/actors/insights/monetization) dashboard under **Development > Insights**. The metrics are organized across the **Monetization**, **Acquisition**, and **Debugging** tabs.
 
-The analytics dashboard allows you to select specific Actors and view key metrics aggregated across all user runs:
+The Insights dashboard allows you to select specific Actors and view key metrics aggregated across all user runs:
 
 - Revenue, costs and profit trends over time
 - User growth metrics (both paid and free users)

diff --git a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx
@@ -23,20 +23,21 @@ If your Actor uses tiered pricing, the user's discount tier determines the unit
 
 The following table summarizes the platform unit costs used for your cost computation across different discount tiers.
 
-| Service (unit)                        | _FREE_  | _BRONZE_ | _SILVER_ | _GOLD_  |
-|:--------------------------------------|--------:|---------:|---------:|--------:|
-| Compute unit (per CU)                 | $0.2    | $0.2     | $0.16    | $0.13   |
-| Residential proxies (per GB)          | $8      | $8       | $7.5     | $7      |
-| SERPs proxy (per 1,000 SERPs)         | $2.5    | $2.5     | $2       | $1.7    |
-| Data transfer - external (per GB)     | $0.2    | $0.2     | $0.19    | $0.18   |
-| Data transfer - internal (per GB)     | $0.05   | $0.05    | $0.045   | $0.04   |
-| Dataset - reads (per 1,000 reads)     | $0.0004 | $0.0004  | $0.00036 | $0.00032|
-| Dataset - writes (per 1,000 writes)   | $0.005  | $0.005   | $0.0045  | $0.004  |
-| Key-value store - reads (per 1,000)   | $0.005  | $0.005   | $0.0045  | $0.004  |
-| Key-value store - writes (per 1,000)  | $0.05   | $0.05    | $0.045   | $0.04   |
-| Key-value store - lists (per 1,000)   | $0.05   | $0.05    | $0.045   | $0.04   |
-| Request queue - reads (per 1,000)     | $0.004  | $0.004   | $0.0036  | $0.0032 |
-| Request queue - writes (per 1,000)    | $0.01   | $0.01    | $0.009   | $0.008  |
+| Service (unit)                       | _FREE_  | _BRONZE_ | _SILVER_ | _GOLD_   |
+|:-------------------------------------|--------:|---------:|---------:|---------:|
+| Compute unit (per CU)                | $0.2    | $0.2     | $0.16    | $0.13    |
+| Residential proxies (per GB)         | $8      | $8       | $7.5     | $7       |
+| SERPs proxy (per 1,000 SERPs)        | $2.5    | $2.5     | $2       | $1.7     |
+| Web Unblocker (per 1,000 units)      | $0.15   | $0.15    | $0.125   | $0.1     |
+| Data transfer - external (per GB)    | $0.2    | $0.2     | $0.19    | $0.18    |
+| Data transfer - internal (per GB)    | $0.05   | $0.05    | $0.045   | $0.04    |
+| Dataset - reads (per 1,000 reads)    | $0.0004 | $0.0004  | $0.00036 | $0.00032 |
+| Dataset - writes (per 1,000 writes)  | $0.005  | $0.005   | $0.0045  | $0.004   |
+| Key-value store - reads (per 1,000)  | $0.005  | $0.005   | $0.0045  | $0.004   |
+| Key-value store - writes (per 1,000) | $0.05   | $0.05    | $0.045   | $0.04    |
+| Key-value store - lists (per 1,000)  | $0.05   | $0.05    | $0.045   | $0.04    |
+| Request queue - reads (per 1,000)    | $0.004  | $0.004   | $0.0036  | $0.0032  |
+| Request queue - writes (per 1,000)   | $0.01   | $0.01    | $0.009   | $0.008   |
 
 If you decide not to offer tiered discounts on your Actor, the unit prices for _FREE_ tier apply. To offer enterprise level services and unlock even cheaper unit prices for enterprise customers, please reach out to us.
 

diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx
@@ -7,7 +7,7 @@ sidebar_position: 2
 
 [Actor tasks](/platform/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what the Actor does, what inputs it uses, and what output to expect. Public tasks also appear in your Actor's **Examples** tab, which helps users discover your Actor through search engines and AI agents. For monetized Actors, this can lead to more page views, more runs, and more revenue.
 
-You can create up to 50 tasks per Actor.
+You can publish up to 50 public tasks per Actor.
 
 ## Prerequisites
 

diff --git a/sources/platform/actors/publishing/publish.mdx b/sources/platform/actors/publishing/publish.mdx
@@ -17,7 +17,7 @@ Once you've finished coding and testing your Actor, it's time to publish it. Fol
 
 ![Actor settings](./images/actor-display-information.webp)
 
-After filling in all the required fields, the **Publish to Store** button will turn green. Click on it to make your Actor available to the public on Apify Store.
+After filling in all the required fields, the **Publish on Store** button will turn green. Click on it to make your Actor available to the public on Apify Store.
 
 ![Publish your Actor](./images/publish-actor-to-store.webp)
 

diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx
@@ -13,7 +13,7 @@ This helps us to flag Actors that temporarily don't work as expected `under main
 ## How we test
 
 The test runs the Actor with its default input (defined by the [**prefill**](https://docs.apify.com/platform/actors/development/actor-definition/input-schema/specification/v1#prefill-vs-default-vs-required) option in the input schema file)
-and expects it to finish with a **Succeeded** status and non-empty default dataset within 5 minutes of the beginning of the run.
+and expects it to finish with a **Succeeded** status within 5 minutes of the beginning of the run.
 
 ![Actor page](./images/actor-test.webp)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -49,4 +49,4 @@ To let your users know that the Actor is no longer being developed, use the **De

		Don't delete the Actor as it might break the existing integrations.

		Note that the deprecated Actors aren't searchable in Apify Store. The Deprecated status is also automatically set when your Actor fails the [automated testing](../development/automated_tests.md) process for 30 days.
		Note that the deprecated Actors aren't searchable in Apify Store. The Deprecated status can also be set automatically if your Actor keeps failing the [automated testing](../development/automated_tests.md) process. In that case, the Actor is first placed Under maintenance after about 3 days, receives a deprecation warning 14 days later, and is set to Deprecated after another 14 days if it remains unfixed.