Plan, usage and limits
What the workspace plan includes, where usage is counted, and what happens at a limit.
On this page
Where this comes from
This guide is distilled from docs/BILLING.md. When the guide and Growth-OS disagree, that document is the one to trust, and the difference is worth reporting.
The plan decides what is available
Plan and entitlements are server-owned policy, not interface decoration. A feature the plan does not include is unavailable and says why, and the same check runs again in the service when you act.
Usage survives retries
Concurrency, billing-period, session and API-key limits use a durable ledger with stable event identity, so a retried request is counted once. Generated drafts, insights and Ask questions all count against the same AI allowance.
Opening a playbook to read it sends nothing. A request is spent when you ask for a reading, a draft or a rewrite.
When you hit a limit
The interface explains which limit was reached and what the next step is. It does not silently degrade a result, and a partial read always says it was partial.
Was this page helpful?
Feedback is stored only in this browser.