Billing wallet
How balances, grants, and usage work in US dollars.
Billing uses a single USD wallet per account. Balances and usage are shown in
dollars (for example, $5.00).
Wallet buckets
| Bucket | Description |
|---|---|
| Monthly included | Plan allowance (Hobby: $5/mo; Pro includes more) |
| Daily login | $1/day Hobby with payment method; $2/day Pro |
| Purchased | Top-ups and other paid FTAI |
The available balance is the sum of remaining grant balances. Monthly usage on the Usage page shows spend against your plan allowance for the current period (for example $0 / $5 used on Hobby).
What is metered
The wallet covers every metered surface, not only chat:
- Model usage - chat turns, Run attempts, and subagent model calls debit input, output, and cache-read tokens at the serving model's rate.
- Browser sessions - browser tool sessions debit measured session duration.
- Web search - managed web-search requests debit each successful search.
- Sandbox compute - sandbox VM operations debit metered active compute seconds at the VM kind's rate; idle lease time between operations is never metered.
Metering events submitted through the Developer API debit the same wallet. The product reserves an estimate before generation and charges the actual amount afterward. The Usage page itemizes spend by surface.
Plan limits (requests per minute, sessions per day, allowed models) are entitlements, not separate wallet lines.
Grant order
When usage is debited, grants are consumed by expiry, not by source: the grant that expires soonest is spent first, and grants with no expiry are spent last. Ties break by creation time (oldest first), then by grant id.
In practice that means daily login FTAI - which expires at the end of its day - goes before the monthly allowance, which goes before top-ups and other grants with a later or absent expiry. Referral, commitment, adjustment, and enterprise grants follow the same rule; a source name never outranks an earlier expiry.