Paw Compute
The single usage meter every runtime consumes.
Paw Compute is a single, weighted usage meter — every runtime (Conversation, Coding, Browser, Office, and others) reports through the same pipeline, so you see one number, never a per-feature limit.
It replaces a flat "one credit per turn" model with a weighted calculation reflecting real backend cost, computed server-side.
Implemented
Plan allowances, weekly limits, credit behavior and organization pooling are account-controlled. Check Settings → Usage and your organization billing screen for current values.
Warning
PawOS documentation describes Paw Compute as a product-level meter. Users do not need to configure or understand the underlying model-provider billing details.
How it works
What you see
- Your plan, Paw Compute usage and limits, Ticket Wallet balance, payment status, and a clear message when a limit or balance stops a request.
- Which activity uses Paw Compute and which uses the Ticket Wallet.
What PawOS does
- Paw Compute measures everyday usage against your plan’s limits.
- The Ticket Wallet is a separate balance used for completed autonomous tickets.
- Plan checks happen before work runs and before plan-restricted connectors are enabled.
Permissions
- Buying Ticket Wallet credits does not change your plan, and changing your plan does not add Ticket Wallet credits.
- A paid plan still asks for approval before actions that change your machine.
- Failed, blocked or unverified autonomous work is never charged.
Records
- Usage and charges show the source, amount, period and remaining balance.
- When something is blocked, PawOS says whether it’s your plan, your usage, your balance or a connection.
Good to know
- Refunds, invoices, taxes and cancellations follow the billing and legal policy pages.