Plans and pricing

Credits, model tiers, and budget stops

Taskcenter uses precise credits and model tiers to make autonomous work understandable. The runtime reserves budget before model/tool work and records actual usage after completion.

Credits

Credits represent agent capacity. Paid model and tool work must reserve available credits before execution. Available credits are included package credits plus owner/admin grants minus used and reserved credits. Credit quantities preserve up to three decimal places so model/tool costs are not rounded down. Zero-credit accounts may still view existing workspace state, but paid runtime work must stop with a clear quota message before spend starts.

Admin credit grants

Workspace owners and admins can add credits through Usage & Billing. Grants are durable credit_grants ledger records, scoped to the actor, normalized to the shared credit precision, audited through the guarded data adapter, and included in the balance shown to the user.

New account grants

Every new password signup receives 300 free credits as a durable system credit_grants row after account creation. If the grant cannot be written, signup reports a clear failure instead of presenting a zero-credit account as ready.

North Star tiers

Lite should cover quick chat and short planning. Pro should cover multi-step work and subagent coordination. Max should be reserved for long-running, evidence-heavy work.

Budget stops

Budget stops are safety rails, not UI decoration. The North Star budget evaluator records a durable warning budget_incident when projected usage reaches 80% of an active quota policy, and a hard-stop incident when the next run would exceed the configured limit. If a run, routine, or child agent would exceed the configured limit, execution should stop and explain what was skipped.