Skip to content

docs: fix high-severity inaccuracies in Actors pages#2725

Open
mtrunkat wants to merge 1 commit into
masterfrom
claude/docs-fix-actors-high-8g4myu
Open

docs: fix high-severity inaccuracies in Actors pages#2725
mtrunkat wants to merge 1 commit into
masterfrom
claude/docs-fix-actors-high-8g4myu

Conversation

@mtrunkat

@mtrunkat mtrunkat commented Jul 2, 2026

Copy link
Copy Markdown
Member

Fixes high-severity discrepancies found while auditing the Actors docs against the platform source (apify-core).

  • programming_interface/index.mdx - the Environment variables card linked to the Container web server page, and the "Status events" card linked to Status messages, leaving the Environment variables and System events pages unreachable from the hub. Card links (and the mistitled card) corrected.
  • publishing/monetize/pricing_and_costs.mdx - the developer cost table listed retail subscription prices instead of the developer platform costs. Compute unit is $0.3/$0.3/$0.25/$0.2 (FREE/BRONZE/SILVER/GOLD) and request-queue writes are double the previously listed values, per the current effective PaidActorDeveloperPricing seed; the BRONZE 10-CU example is now $3.
  • running/store/index.md - the intro said "four pricing models" but listed only three. Added the missing pay-per-result model (PRICE_PER_DATASET_ITEM).

Generated by Claude Code

- 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
Copilot AI review requested due to automatic review settings July 2, 2026 20:01
@apify-service-account

apify-service-account commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit b556ddd) is ready at https://pr-2725.preview.docs.apify.com (see action run).

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR corrects several high-severity inaccuracies in the Actors documentation to better match current platform behavior and pricing, and to restore navigation to key programming-interface pages.

Changes:

  • Restored correct hub navigation by fixing broken Card links and renaming the “Status events” Card to “System events”.
  • Corrected the developer platform cost example and updated unit-cost values (compute units and request-queue writes) in the pricing table.
  • Added the missing “Pay per result” pricing model to match the “four pricing models” claim and documented it as a legacy model.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
sources/platform/actors/running/store/index.md Adds and documents the missing “Pay per result” pricing model section so the pricing-model list matches the intro statement.
sources/platform/actors/publishing/monetize/pricing_and_costs.mdx Updates the cost example and unit-cost table values to reflect current developer platform costs.
sources/platform/actors/development/programming_interface/index.mdx Fixes broken hub Card routing and corrects the “System events” Card title/link so pages are reachable from the hub.

:::

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.2/CU, your cost would be $2.
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.
@mtrunkat mtrunkat added the adhoc Ad-hoc unplanned task added during the sprint. label Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants