Merge branch 'master' into feat/n8n-wcc-docs

Author: protoss70

apify-api/openapi/components/schemas/actors/UpdateActorRequest.yaml

@@ -50,3 +50,24 @@ properties:
     oneOf:
       - nullable: true
       - $ref: ./DefaultRunOptions.yaml
+  taggedBuilds:
+    type: object
+    description: |
+      Object containing the Actor's tagged builds, where the key is the tag name (e.g., _latest_) and the value is an object containing the build ID.
+      The object you provide will completely overwrite all existing tagged builds for the Actor.
+
+      - To create or reassign a tag: Include it in the object with the desired `buildId`.
+      - To remove a specific tag: Submit the object without that tag's key.
+      - To remove all tags: Provide an empty object: `{}`.
+      - If this field is omitted or `null`, the existing tags will not be changed.
+    nullable: true
+    additionalProperties:
+      type: object
+      required:
+        - buildId
+      properties:
+        buildId:
+          type: string
+    example:
+      latest:
+        buildId: z2EryhbfhgSyqj6Hn

apify-api/openapi/paths/actor-runs/actor-runs@{runId}@charge.yaml

@@ -7,6 +7,12 @@ post:
     The event you are charging for must be one of the configured events in your Actor. If the Actor is not set up as pay per event, or if the event is not configured,
     the endpoint will return an error. The endpoint must be called from the Actor run itself, with the same API token that the run was started with.
 
+    :::info Learn more about pay-per-event pricing
+
+    For more details about pay-per-event (PPE) pricing, refer to our [PPE documentation](/platform/actors/publishing/monetize/pay-per-event).
+
+    :::
+
   operationId: PostChargeRun
   parameters:
     - name: runId

apify-api/openapi/paths/datasets/datasets@{datasetId}@items.yaml

@@ -367,6 +367,14 @@ get:
       schema:
         type: boolean
         example: false
+    - name: signature
+      in: query
+      description: Signature used to access the items.
+      required: false
+      style: simple
+      schema:
+        type: string
+        example: 2wTI46Bg8qWQrV7tavlPI
   responses:
     '200':
       description: ''

apify-api/openapi/paths/key-value-stores/key-value-stores@{storeId}@keys.yaml

@@ -48,6 +48,14 @@ get:
       schema:
         type: string
         example: post-images-
+    - name: signature
+      in: query
+      description: Signature used to access the keys.
+      required: false
+      style: simple
+      schema:
+        type: string
+        example: 2wTI46Bg8qWQrV7tavlPI
   responses:
     '200':
       description: ''

apify-api/openapi/paths/key-value-stores/key-value-stores@{storeId}@records@{recordKey}.yaml

@@ -32,6 +32,14 @@ get:
       schema:
         type: string
         example: someKey
+    - name: signature
+      in: query
+      description: Signature used to access the record.
+      required: false
+      style: simple
+      schema:
+        type: string
+        example: 2wTI46Bg8qWQrV7tavlPI
   responses:
     '200':
       description: ''

package-lock.json

@@ -46,24 +46,18 @@
     "devDependencies": {
         "@apify/eslint-config": "^1.0.0",
         "@apify/tsconfig": "^0.1.0",
-        "@rsbuild/plugin-styled-components": "^1.1.0",
         "@types/react": "^19.0.0",
         "babel-plugin-styled-components": "^2.1.4",
         "cross-env": "^7.0.3",
         "eslint": "^9.32.0",
-        "eslint-plugin-json": "^4.0.1",
-        "eslint-plugin-markdown": "^5.1.0",
         "eslint-plugin-react": "^7.37.5",
-        "eslint-plugin-react-hooks": "^5.2.0",
-        "fs-extra": "^11.1.1",
         "globals": "^16.0.0",
-        "globby": "^14.0.0",
         "markdownlint": "^0.38.0",
         "markdownlint-cli": "^0.45.0",
         "patch-package": "^8.0.0",
         "path-browserify": "^1.0.1",
         "rimraf": "^6.0.0",
-        "typescript": "5.9.2",
+        "typescript": "5.9.3",
         "typescript-eslint": "^8.38.0"
     },
     "dependencies": {
@@ -75,27 +69,21 @@
         "@docusaurus/preset-classic": "^3.8.1",
         "@docusaurus/theme-common": "^3.8.1",
         "@docusaurus/theme-mermaid": "^3.8.1",
-        "@docusaurus/utils": "^3.8.1",
         "@giscus/react": "^3.0.0",
-        "@mdx-js/react": "^3.0.1",
         "@redocly/cli": "^1.27.1",
         "@signalwire/docusaurus-plugin-llms-txt": "^1.2.1",
-        "ajv": "^8.17.1",
         "clsx": "^2.0.0",
         "docusaurus-plugin-image-zoom": "^3.0.1",
         "docusaurus-plugin-openapi-docs": "^4.3.7",
         "docusaurus-theme-openapi-docs": "^4.3.7",
-        "form-data": "^4.0.0",
         "github-buttons": "^2.28.0",
         "postcss-preset-env": "^10.0.0",
         "prism-react-renderer": "^2.4.0",
         "prop-types": "^15.8.1",
-        "proxy-from-env": "^1.1.0",
         "raw-loader": "^4.0.2",
         "react": "^19.1.0",
         "react-dom": "^19.1.0",
         "react-github-btn": "^1.4.0",
-        "search-insights": "2.17.3",
         "styled-components": "6.1.19",
         "unist-util-visit": "^5.0.0"
     },

package.json

@@ -251,6 +251,12 @@ Common issues and solutions:
 
 Apify's pay-per-event (PPE) pricing model allows charging users based on specific triggered events through the API or SDKs.
 
+:::info How pay-per-event pricing works
+
+If you want more details about PPE pricing, refer to our [PPE documentation](/platform/actors/publishing/monetize/pay-per-event).
+
+:::
+
 ### Step 1: Define chargeable events
 
 You can configure charges for events like the Actor starting, a task completing successfully, or custom events such as specific API calls.

sources/academy/ai/ai-agents.mdx

@@ -33,7 +33,11 @@ Monetizing your Actor on the Apify platform involves several key steps:
   - 2nd user starts their trial but pays next month.
   - 3rd user on a free plan finishes the trial without upgrading to a paid plan and can’t use the Actor further.
 
-Learn more about the rental pricing model in our [documentation](/platform/actors/publishing/monetize#rental-pricing-model).
+:::info Rental pricing details
+
+If you want more details about rental pricing, refer to our [rental pricing documentation](/platform/actors/publishing/monetize/rental).
+
+:::
 
 ### Pay-per-result pricing model
 
@@ -49,7 +53,11 @@ Learn more about the rental pricing model in our [documentation](/platform/actor
   - 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.
 
-Learn more about the pay-per-result pricing model in our [documentation](/platform/actors/publishing/monetize#pay-per-result-pricing-model).
+:::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).
+
+:::
 
 ### Pay-per-event pricing model
 
@@ -77,7 +85,11 @@ Learn more about the pay-per-result pricing model in our [documentation](/platfo
     - This comes up to $1.625 of total revenue
   - That means if platform usage costs are $0.365 for user A and $0.162 for user B your profit is $4.748
 
-Learn more about the pay-per-event pricing model in our [documentation](/platform/actors/publishing/monetize#pay-per-event-pricing-model).
+:::info Pay-per-event details
+
+If you want more details about PPE pricing, refer to our [PPE documentation](/platform/actors/publishing/monetize/pay-per-event).
+
+:::
 
 ## Setting up monetization
 
@@ -104,7 +116,7 @@ The easiest way to understand your tool's value is to look around. Are there sim
 
 Try competitor tools yourself (to assess the value and the quality they provide), check their SEO (to see how much traffic they get), and note ballpark figures. Think about what your Actor can do that competitors might be missing.
 
-Also, remember that your Actor is a package deal with the Apify platform. So all the platform's features automatically transfer onto your Actor and its value. Scheduling, monitoring runs, ways of exporting data, proxies, and integrations can all add value to your Actor (on top of its own functionalities). Be sure to factor this into your tool's value proposition and communicate that to the potential user.
+Also, remember that your Actor is a package deal with the Apify platform. All the platform's features automatically transfer onto your Actor and its value. Scheduling, monitoring runs, ways of exporting data, proxies, and integrations can all add value to your Actor (on top of its own functionalities). Be sure to factor this into your tool's value proposition and communicate that to the potential user.
 
 ### Do research in Apify Store
 
@@ -114,13 +126,19 @@ Learn more about what makes a good readme here: [How to create an Actor README](
 
 ### Rental, pay-per-result (PPR), or pay-per-event (PPE)
 
-Rental pricing is technically easier: you set the rental fee, and the user covers their CU usage. So all you have to define is how much you want to charge the users. With pay-per-result, you’ll need to include both CU usage and your margin. So you have to calculate how much the average run is going to cost for the user + define how much you want to charge them.
+Rental pricing allows you to charge a monthly fee for your Actor and users cover their own compute 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.
 
-To figure out the average cost per run for users, just run a few test runs and look at the statistics in the Actor [**Analytics**](https://console.apify.com/actors?tab=analytics) tab.
+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.
 
-From an average user's perspective, pay-per-result is often easier to grasp — $25 for a thousand pages, $5 for a thousand videos, $1 for a thousand images, etc. It gives users a clearer idea of what they’re paying for and allows them to estimate faster. But rental pricing has its fans, too — if your tool provides high value, users will come.
+:::tip Additional benefits
+
+Actors that implement PPE receive additional benefits, including increased visibility in Apify Store and enhanced discoverability.
+
+:::
 
-Pay-per-event (PPE) lets you define pricing for individual events. You can charge for specific events directly from your Actor by calling our PPE charging API. The most common events will most likely be Actor start, dataset item, external API calls, etc. PPE is great for users who want to optimize their costs and value transparency. PPE is also a fairer pricing model for integration and AI-driven use cases, where dataset-based pricing doesn’t make sense.
+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
 

sources/academy/platform/get_most_of_actors/store_basics/how_actor_monetization_works.md

@@ -35,7 +35,7 @@ The following table compares the two main pricing models available for monetizin
 | AI/MCP compatibility    | ❌ Not compatible             | ✅ Fully compatible           | ✅ Fully compatible           |
 | User cost predictability| Unpredictable (rental + usage)    | Predictable    | Predictable    |
 | Store discounts         | ❌ Single price only          | ✅ Store discounts available  | ✅ Store discounts available  |
-| Marketing boost         | Standard visibility           | Priority store placement      | Priority store placement      |
+| Marketing boost         | Standard visibility           | Standard visibility           | Priority store placement      |
 | Commission opportunities| Standard 20%                  | Standard 20%                  | Promotional 0% periods        |
 | Custom event billing    | Not available                 | Not available                 | ✅ Charge for any event       |
 | Per-result billing      | Not available                 | ✅ Charge per dataset item    | Optional (via event)          |