docs(pricing): explain app invocation billing

[ehfeng]

Description

Explain how app invocations are billed, including:

• the per-second invocation rate and underlying GB-second calculation
• when invocation metering starts and stops
• billing behavior for failed and canceled invocations
• separate browser and third-party service charges
• the distinction between usage billing and concurrency limits

The usage table now presents invocation and browser rates in the same $/sec format.

Implementation Checklist

• No sample app changes
• No CLI changes

Testing

• git diff --check
• mintlify dev using Node 22
• Confirmed /info/pricing returns successfully and contains the new rate and section

Docs

• This is the docs repo

Visual Proof

Validated the rendered pricing page locally at /info/pricing.

Related Issue

N/A

Additional Notes

The default machine runtime is Node 26, which Mintlify does not support, so local validation used Node 22.

---

Note

Low Risk
Documentation-only updates to pricing and invoke pages with no product, API, or billing logic changes.

Overview
Documents app invocation usage pricing and how it relates to browsers and third-party services.

On /info/pricing, the usage table is relabeled from browser-only types to Usage type, browser rows are clarified, and a new App invocation line is added at $0.0000666668/sec. A new FAQ accordion explains active compute billing (GB-second basis), start/stop metering, charges on failed/canceled runs, separate browser and external API costs, and that plan limits are concurrency, not included invocations. A small MDX fix closes the Managed Auth accordion properly.

On /apps/invoke, a short note under Return values points readers to that FAQ and states that invocation compute is billed separately from browsers created during a run.

^{Reviewed by Cursor Bugbot for commit 4a0f989. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 8, 2026, 5:18 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-08T17:21:31.379081Z	8ad815b	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 8ad815b. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8ad815b045

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Rewrite the billing explanation in active, second-person voice

The opening explanation uses passive, third-person phrasing (App invocations are billed), and the section repeats this pattern for browser billing. Address the reader directly—for example, explain what you pay for—so the new documentation follows the repository's required active, second-person style.

AGENTS.md reference: AGENTS.md:L4-L5

Useful? React with 👍 / 👎.

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Prior approval stands. Not re-approving (already approved on the previous commit). Risk did not increase after this update, so approval is not revoked.

Re-evaluation (synchronize): HEAD is 49a1516. The previous approval was on 8ad815b. The incremental change stays on the same file and remains documentation-only: the usage table is renamed from Browser type to Usage type, an App invocation rate row is added, browser row labels are clarified, and derived per-minute/per-hour/example cost copy is removed in favor of pointing at the table rate.

Current scope vs main: info/pricing.mdx only (+16 / −5). No application code, billing logic, APIs, auth, infrastructure, config, or CODEOWNERS-covered ownership files.

Why Very Low

• Documentation-only MDX change on a docs site
• Small, isolated surface area with no production logic or shared systems
• No CODEOWNERS file and no required ownership review
• Update after approval is editorial/table-structure only; blast radius is unchanged

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Prior approval stands. Not re-approving (already approved). Risk did not increase after this update, so approval is not revoked.

Re-evaluation (synchronize): HEAD is 90be02f. Prior approval is on 8ad815b; the last assessment was on 49a1516. The incremental change is still documentation-only: the invocation billing explanation moved from a dedicated section into an FAQ accordion, and apps/invoke.mdx gained a two-line pointer to that FAQ.

Current scope vs main: info/pricing.mdx and apps/invoke.mdx only (+17 / −6). No application code, billing logic, APIs, auth, infrastructure, config, or CODEOWNERS-covered ownership files.

Why Very Low

• Documentation-only MDX changes on a docs site
• Small, isolated surface area with no production logic or shared systems
• No CODEOWNERS file and no required ownership review
• Update after approval is editorial (FAQ move + cross-link); blast radius is unchanged

  

_{Sent by Cursor Automation: Assign PR reviewers}

[Jayko001]

Please address the inline placement comment.

[Jayko001]

Could we move this pricing note to the end of the page?

[cursor]

Risk assessment: Very Low

Decision: Prior approval stands. Not re-approving (already approved on an earlier commit). Risk did not increase after this update, so approval is not revoked.

Re-evaluation (synchronize): HEAD is 4a0f989. Prior approval is on 8ad815b; the last assessment was on 90be02f. The incremental change is documentation-only: the app-invocation pricing note in apps/invoke.mdx moved from the top of the page to the end of the Return values section.

Current scope vs main: info/pricing.mdx and apps/invoke.mdx only (+17 / −6). No application code, billing logic, APIs, auth, infrastructure, config, or CODEOWNERS-covered ownership files.

Why Very Low

• Documentation-only MDX changes on a docs site
• Small, isolated surface area with no production logic or shared systems
• No CODEOWNERS file and no required ownership review
• Update after approval is editorial (note placement); blast radius is unchanged

  

_{Sent by Cursor Automation: Assign PR reviewers}

Replacing this review with an applyable suggested change.