docs: PPR cleanup in creator facing docs (#2326)

## Summary

- Remove all PPR (pay-per-result) references from creator-facing docs
- Delete the `pay_per_result.mdx` page and orphaned PPR images
- Update monetization comparison table and pricing model lists to PPE +
Rental only
- Fix broken links (missing hrefs, absolute → relative URLs)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk documentation-only changes that remove the deprecated PPR
pricing model from creator-facing guides and adjust links/tables
accordingly; main risk is broken or missed cross-references in docs
navigation.
> 
> **Overview**
> Removes creator-facing documentation for the deprecated
*pay-per-result (PPR)* model, including deleting the
`pay_per_result.mdx` page and stripping PPR sections/examples from
monetization guidance.
> 
> Updates monetization docs to present only **pay-per-event (PPE)** and
**rental**, including revised comparison tables, pricing model lists,
and related wording (e.g., `pricing_and_costs.mdx`, `pay_per_event.mdx`,
publishing pages). Also fixes/normalizes several internal links and adds
the `RentalSunset` notice to the monetization index.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
6ec40ee. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Priban

.gitignore

@@ -30,3 +30,4 @@ sources/academy/**/exercises/storage
 sources/academy/**/exercises/node_modules
 sources/academy/**/exercises/package*.json
 sources/academy/**/exercises/dataset.json
+.claude/worktrees/

sources/academy/build-and-publish/apify-store-basics/how_actor_monetization_works.md

@@ -66,26 +66,6 @@ If you want more details about PPE pricing, refer to our [PPE documentation](/pl
 
 :::
 
-### Pay-per-result pricing model
-
-![pay per result model example](images/ppr-model.png)
-
-- _How it works_: you charge users based on the number of results your Actor generates. You earn 80% of the revenue minus platform usage costs.
-- _Profit calculation_: `profit = (0.8 * revenue) - platform usage costs`
-- _Cost breakdown_:
-  - Compute unit: $0.3 per CU
-  - Residential proxies: $13 per GB
-  - SERPs proxy: $3 per 1,000 SERPs
-  - Data transfer (external): $0.20 per GB
-  - Dataset storage: $1 per 1,000 GB-hours
-- _Example_: you set a price of $1 per 1,000 results. Two users generate 50,000 and 20,000 results, paying $50 and $20, respectively. If the platform usage costs are $5 and $2, your profit is $49.
-
-:::info Pay-per-result details
-
-If you want more details about PPR pricing, refer to our [PPR documentation](/platform/actors/publishing/monetize/pay-per-result).
-
-:::
-
 ### Rental pricing model
 
 <RentalSunset/>
@@ -148,26 +128,12 @@ Apify Store is like any other marketplace, so take a look at your competition th
 
 Learn more about what makes a good readme here: [How to create an Actor README](/academy/actor-marketing-playbook/actor-basics/how-to-create-an-actor-readme)
 
-### Pay-per-event (PPE), pay-per-result (PPR), or rental
-
-Pay-per-event (PPE) gives you the most flexibility and growth potential. You can charge for any meaningful event your Actor performs (for example, page scraped, browser page opened, or an external API call). This makes costs predictable for users, lets you model value precisely, and is fully compatible with AI and MCP-based integrations.
-
-Rental pricing allows you to charge a monthly fee for your Actor and users cover their own platform usage.
-
-Pay-per-result (PPR) charges users based on the number of items your Actor adds to the dataset. This model works best when each dataset item represents clear value to the user - like scraped product listings, extracted contact information, or processed documents.
-
-:::tip Additional benefits
-
-Actors that implement PPE receive additional benefits, including increased visibility in Apify Store and enhanced discoverability.
+### Adapt when needed
 
-:::
+Don’t be afraid to experiment with pricing, especially at the start. You can monitor your results in the dashboard and adjust if necessary. You can also choose to [pass platform usage costs to users](/platform/actors/publishing/monetize/pay-per-event#pass-platform-usage-to-users) while you’re still figuring out the right price.
 
 To estimate pricing, run a few test runs and review the statistics in the Actor [**Analytics**](https://console.apify.com/actors?tab=analytics) tab.
 
-### Adapt when needed
-
-Don’t be afraid to experiment with pricing, especially at the start. You can monitor your results in the dashboard and adjust if necessary.
-
 Keep an eye on SEO as well. If you monitor the volume of the keywords your Actor is targeting as well as how well your Actor's page is ranking for those keywords, you can estimate the number of people who actually end up trying your tool (aka conversion rate). If your keywords are getting volume, but conversions are lower than expected, it might point to a few issues It could be due to your pricing, a verbose README, or complex input. If users are bouncing right away, it makes sense to check out your pricing and your closest competitors to see where adjustments might help.
 
 ### Summary & a basic plan
@@ -184,15 +150,15 @@ Example of useful pricing estimates from the **Analytics** tab:
 
 :::tip Use emails!
 
-📫 Don't forget to set an email sequence to warn and remind your users about pricing changes. Learn more about emailing your users here:  [Emails to Actor users]
+📫 Don't forget to set an email sequence to warn and remind your users about pricing changes. Learn more about emailing your users here:  [Emails to Actor users](/academy/actor-marketing-playbook/interact-with-users/emails-to-actor-users)
 
 :::
 
 ## Resources
 
 - Learn about [incentives behind monetization](https://apify.com/partners/actor-developers)
-- Detailed guide to [setting up monetization models](https://docs.apify.com/academy/get-most-of-actors/monetizing-your-actor)
-- Guide to [publishing Actors](https://docs.apify.com/platform/actors/publishing)
+- Detailed guide to [setting up monetization models](/platform/actors/publishing/monetize)
+- Guide to [publishing Actors](/platform/actors/publishing)
 - Watch our webinar on how to [build, publish and monetize Actors](https://www.youtube.com/watch?v=4nxStxC1BJM)
 - Read a blog post from our CEO on the [reasoning behind monetizing Actors](https://blog.apify.com/make-regular-passive-income-developing-web-automation-actors-b0392278d085/)
 - Learn about the [Creator plan](https://apify.com/pricing/creator-plan), which allows you to create and freely test your own Actors for $1

sources/academy/build-and-publish/apify-store-basics/how_store_works.md

@@ -40,7 +40,6 @@ Actors on Apify Store can be public or private:
 You can monetize your Actors using three different pricing models:
 
 - Pay for usage: charge based on how much the Actor is used.
-- Pay per result: the price is based on the number of results produced, with the first few free.
 - Pay per event: the price is based on specific events triggered by the Actor.
 - Monthly billing: set a fixed monthly rental rate for using the Actor.
 

sources/academy/build-and-publish/apify-store-basics/images/ppr-model.png

@@ -74,7 +74,7 @@ Once set, the page URL should not be changed. Because of those two important rea
 
 If you absolutely have to change the URL, you will have to communicate that fact to your users.
 
-💡 Learn more about the easiest ways to communicate with your users: [Emails to Actor users]
+💡 Learn more about the easiest ways to communicate with your users: [Emails to Actor users](/academy/actor-marketing-playbook/interact-with-users/emails-to-actor-users)
 
 ## How and where to set the Actor URL
 

sources/academy/build-and-publish/apify-store-basics/importance_of_actor_url.md

@@ -23,7 +23,7 @@ While most Actors on Apify Store are web scrapers or crawlers, there are ever mo
 By publishing your service or project at [Apify Store](https://apify.com/store) your project will benefit from:
 
 1. _Expanded reach_: Your tool instantly becomes available to Apify's user community and connects with popular automation platforms like [Make](https://www.make.com), [n8n](https://n8n.io/), and [Zapier](https://zapier.com/).
-2. _Multiple monetization paths_: Choose from flexible pricing models (monthly subscriptions, pay-per-result, or pay-per-event).
+2. _Multiple monetization paths_: Choose from flexible pricing models (pay-per-event or monthly subscriptions).
 3. _AI integration_: Your Actor can serve as a tool for AI agents through Apify's MCP (Model Context Protocol) server, creating new use cases and opportunities while you earn 80% of all revenues.
 
 :::tip Open-Source Benefits

sources/academy/build-and-publish/how-to-build/actorization_playbook.mdx

@@ -84,7 +84,7 @@ Actor `name`, `version`, `buildTag`, and `environmentVariables` are currently on
 | `storages.datasets` | Optional | You can define multiple datasets for the Actor under the `storages.datasets` field. This can be an object containing embedded objects or paths to a JSON schema files. [Read more](/platform/actors/development/actor-definition/dataset-schema/multiple-datasets) about multiple dataset schemas. |
 | `defaultMemoryMbytes` | Optional | Specifies the default amount of memory in megabytes to be used when the Actor is started. Can be an integer or a [dynamic memory expression string](./dynamic_actor_memory/index.md). |
 | `minMemoryMbytes` | Optional | Specifies the minimum amount of memory in megabytes required by the Actor to run. Requires an _integer_ value. If both `minMemoryMbytes` and `maxMemoryMbytes` are set, then `minMemoryMbytes` must be equal or lower than `maxMemoryMbytes`. Refer to the [Usage and resources](https://docs.apify.com/platform/actors/running/usage-and-resources#memory) for more details about memory allocation. |
-| `maxMemoryMbytes` | Optional | Specifies the maximum amount of memory in megabytes required by the Actor to run. It can be used to control the costs of run, especially when developing pay per result Actors. Requires an _integer_ value. Refer to the [Usage and resources](https://docs.apify.com/platform/actors/running/usage-and-resources#memory) for more details about memory allocation. |
+| `maxMemoryMbytes` | Optional | Specifies the maximum amount of memory in megabytes required by the Actor to run. It can be used to control the costs of run. Requires an _integer_ value. Refer to the [Usage and resources](https://docs.apify.com/platform/actors/running/usage-and-resources#memory) for more details about memory allocation. |
 | `usesStandbyMode` | Optional | Boolean specifying whether the Actor will have [Standby mode](../programming_interface/actor_standby.md) enabled. |
 | `webServerSchema` | Optional | Defines an OpenAPI v3 schema for the web server running in the Actor. This can be either an embedded object or a path to a JSON schema file. Use this when your Actor starts its own HTTP server and you want to describe its interface. |
 | `webServerMcpPath` | Optional | The HTTP endpoint path where the Actor exposes its MCP (Model Context Protocol) server functionality. When set, the Actor is recognized as an MCP server. For example, setting `"/mcp"` designates the `/mcp` endpoint as the MCP interface. This path becomes part of the Actor's stable URL when [Standby mode](../programming_interface/actor_standby.md) is enabled. |

sources/platform/actors/development/actor_definition/actor_json.md

@@ -32,11 +32,10 @@ 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:
 
-- Fixed rental fee for continuous access
-- Pay-per-result for usage-based pricing
 - Pay-per-event for specific operations
+- Fixed rental fee for continuous access
 
-To learn more, visit the [Actors in Store](https://docs.apify.com/platform/actors/running/actors-in-store#pricing-models) page.
+To learn more, visit the [Actors in Store](/platform/actors/running/actors-in-store#pricing-models) page.
 
 ## Maintain public Actors