Usage, quota, and tokens

Polka Codes uses platform tokens for workflow and tool usage. Use this article when you need to understand quota, wallet tokens, or why new billable work is blocked.

How allocation works

1. Paid requests consume both the five-hour burst quota and the 30-day plan allowance. Each allowance resets in full at the end of its own fixed period.
2. When plan quota is exhausted, Polka Codes uses purchased wallet tokens.
3. Purchased tokens do not expire.
4. If neither plan quota nor purchased wallet tokens can cover new billable work, Polka Codes blocks it until the quota resets or you add tokens.

Check current usage

1. Open Settings.
2. Select Usage.
3. Review Current month usage for charged token usage by source.
4. Review Plan quota for the five-hour burst and 30-day quota, remaining tokens, and reset times.

Check wallet tokens and alerts

1. Open Settings.
2. Select Billing.
3. Review Token Wallet.
4. Use Low-Balance Alerts if you want a warning when wallet tokens fall below your chosen threshold.

What counts as usage

Chat work, tool use, sandbox execution, and advanced tools can all consume tokens. Advanced tool usage appears under Tool details in Settings when usage data is available.

Isolated sandbox pricing

Sandbox running time is charged from the shared token system using the selected compute size. The current customer-facing rates are:

• 0.25 vCPU: 30 app tokens per running second.
• 0.5 vCPU: 60 app tokens per running second.
• 1 vCPU: 120 app tokens per running second.
• 2 vCPU: 240 app tokens per running second.
• 4 vCPU: 480 app tokens per running second.

These are Polka Codes customer rates for isolated compute. Each sandbox session has a one-second minimum. Browser Run is billed separately.

Ask for product support in chat if usage looks wrong or a quota message does not match the values shown in Settings.