From b556dddee64aab9c0502240c35b67e12303fa7ac Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Jul 2026 19:45:58 +0000 Subject: [PATCH 1/5] docs: fix high-severity inaccuracies in Actors pages - programming_interface/index.mdx: fix Environment variables card link (was container-web-server) and System events card (retitled from Status events, link was status-messages) - publishing/monetize/pricing_and_costs.mdx: correct compute-unit cost ($0.3/$0.3/$0.25/$0.2) and request-queue write cost (double the previous values), and the BRONZE example ($3) - running/store/index.md: add the missing pay-per-result pricing model so the list matches the stated four models --- .../actors/development/programming_interface/index.mdx | 6 +++--- .../actors/publishing/monetize/pricing_and_costs.mdx | 6 +++--- sources/platform/actors/running/store/index.md | 7 +++++++ 3 files changed, 13 insertions(+), 6 deletions(-) diff --git a/sources/platform/actors/development/programming_interface/index.mdx b/sources/platform/actors/development/programming_interface/index.mdx index b51c87ddc2..5f9d0312b9 100644 --- a/sources/platform/actors/development/programming_interface/index.mdx +++ b/sources/platform/actors/development/programming_interface/index.mdx @@ -19,7 +19,7 @@ This chapter will guide you through all the commands you need to build your firs From 0b87716ba3d5729ef5c701d2a25cacce2ee5a6f8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Trunk=C3=A1t?= Date: Fri, 3 Jul 2026 08:48:15 +0200 Subject: [PATCH 2/5] Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../platform/actors/publishing/monetize/pricing_and_costs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx index 2badfd394e..0cc7bc52e7 100644 --- a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx +++ b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx @@ -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.3/CU, your cost would be $3. +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.3/CU, your cost would be $3. 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. From 8aae3b56b6e5b280bb297d60ec21fc2715e469bb Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 3 Jul 2026 06:52:03 +0000 Subject: [PATCH 3/5] docs: revert platform pricing values and drop pay-per-result Per maintainer review: the original compute-unit ($0.2/$0.2/$0.16/$0.13), request-queue write costs, and the BRONZE example were correct - revert them. Remove the pay-per-result model (being deprecated) from the Store pricing list and correct the count to three. --- .../actors/publishing/monetize/pricing_and_costs.mdx | 6 +++--- sources/platform/actors/running/store/index.md | 9 +-------- 2 files changed, 4 insertions(+), 11 deletions(-) diff --git a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx index 0cc7bc52e7..267826b884 100644 --- a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx +++ b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx @@ -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 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.3/CU, your cost would be $3. +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. @@ -25,7 +25,7 @@ The following table summarizes the platform unit costs used for your cost comput | Service (unit) | _FREE_ | _BRONZE_ | _SILVER_ | _GOLD_ | |:--------------------------------------|--------:|---------:|---------:|--------:| -| Compute unit (per CU) | $0.3 | $0.3 | $0.25 | $0.2 | +| 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 | @@ -36,7 +36,7 @@ The following table summarizes the platform unit costs used for your cost comput | 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.02 | $0.02 | $0.018 | $0.016 | +| 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/running/store/index.md b/sources/platform/actors/running/store/index.md index 05c80db304..ca65c8c14b 100644 --- a/sources/platform/actors/running/store/index.md +++ b/sources/platform/actors/running/store/index.md @@ -18,12 +18,11 @@ import RentalSunset from '../../../../_partials/_rental-sunsetting.mdx'; ## Pricing models -All Actors in [Apify Store](https://apify.com/store) fall into one of the four pricing models: +All Actors in [Apify Store](https://apify.com/store) fall into one of the three pricing models: 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 @@ -72,12 +71,6 @@ _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. - -Pay per result is a legacy pricing model. New Actors are published under [pay per event](#pay-per-event) instead, but you may still encounter existing Actors that use it. - ### Rental Actors From ebe5f2c474be92a35b549ecfe2f7b8d96730a49c Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 3 Jul 2026 06:57:20 +0000 Subject: [PATCH 4/5] chore: re-trigger CI (flaky apify-cli nginx content-type check) From c08135b22835087768af48a4ff31d1dda295a5c2 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 3 Jul 2026 08:20:44 +0000 Subject: [PATCH 5/5] docs: restore pay-per-result as the fourth Store pricing model --- sources/platform/actors/running/store/index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/sources/platform/actors/running/store/index.md b/sources/platform/actors/running/store/index.md index ca65c8c14b..93e63cda79 100644 --- a/sources/platform/actors/running/store/index.md +++ b/sources/platform/actors/running/store/index.md @@ -18,11 +18,12 @@ import RentalSunset from '../../../../_partials/_rental-sunsetting.mdx'; ## Pricing models -All Actors in [Apify Store](https://apify.com/store) fall into one of the three pricing models: +All Actors in [Apify Store](https://apify.com/store) fall into one of the four pricing models: 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 @@ -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