Usage, CU & billing
Included chat usage, optional extra CU and the API wallet are separate balances.
Three balances
Subscription chat and eligible CLI work use included CU. Extra chat CU require explicit spending opt-in. Native API requests use prepaid USD. One CU represents $0.01 at published customer rates; fractional usage is preserved and CU is not withdrawable money.
First-use and rolling windows
A five-hour period begins on first use after the previous one expires. In a rolling seven-day window, each settled debit becomes available seven days later. There is no hidden monthly allowance. Published plan cards and your account show the current limits.
Extra usage
Extra chat spending requires an active subscription and explicit opt-in. Enabling it never buys credit automatically. Extra CU survive subscription renewal. Expiry/refund terms are shown before purchase. API top-ups remain separate and automatic recharge is off.
Reservations and exact rates
The server reserves a bounded worst-case cost before dispatch, then settles measured input/cache/output at the applicable immutable rate version. Unused reservations release; unknown usage remains pending.
Payment lifecycle
Hosted checkout return URLs never grant entitlement. Verified payment events and idempotent ledger transitions do. Billing can show invoices, pending recovery, cancellation and explicit renewal resumption; use the portal or account controls for an actual subscription.