Account
Understand plans and credits
Read the published offer, choose the wallet for the next run and distinguish reserved from settled usage.
Before you begin
- An approved published offer before any purchase.
- A confirmed account and, for team spending, current membership in the intended team.
Follow the steps
Read the whole offer
Open Plans and credits. When an offer is published, read its currency, monthly price, allowance, concurrency, seats, model rates and effective terms together. Do not treat a draft or pending card as a purchasable price.
Checkpoint: You can identify the published offer/version and its conditions, or stop because it remains pending.
Choose personal or team scope
Check the scope shown before Send or checkout. A team wallet belongs to the selected team; membership does not merge private local projects.
Checkpoint: The intended wallet is named before you authorize a new run. Changing the selector affects future runs only.
Read the estimate before sending
Review selected context, model profile and the bounded estimate. Separate usable posted credits, active reservations and available credits.
Checkpoint: The estimate and wallet can cover the allowed work; missing account data is not displayed as a zero-cost run.
Confirm any purchase from the account
If hosted checkout becomes available, use only the published offer for the selected scope. After returning, read the server account/subscription record.
Checkpoint: The account confirms the purchase/grant, or shows Processing/Canceled. A success-looking return URL alone grants nothing.
Read the final usage record
After a run, compare its reservation and settled receipt. Known-unused amounts may be released; missing usage remains pending.
Checkpoint: You can tell what was settled and what is unresolved without assuming a timeout or model failure was free.
Check allowance conditions
Read the current approved plan and its eligibility conditions. Included allowances renew monthly and do not roll over. Do not assume a top-up or Student offer is available unless it is explicitly published.
Checkpoint: You understand which credits are usable now and which future date or eligibility rule affects them.
Check the result
- A named offer, wallet and estimate precede a purchase/run; authoritative records confirm the resulting subscription and usage.
- Canceling a run or a native failure does not erase model usage already incurred.
If something goes wrong
A payment return is Processing or the expected grant is missing.
Keep the checkout reference and reread the same account record. Ask Support to inspect that attempt rather than opening repeated checkouts.
Resume from: Authoritative outcome for the original checkout.
Usage is pending or a reservation remains held.
Keep the run/reference and original scope. Do not assume a refund or switch to another wallet to continue the uncertain request.
Resume from: Settled receipt or explicit unresolved status.
The displayed scope is wrong or eligibility is insufficient.
Do not send. Correct the scope for a new request or review the available plan.
Resume from: Fresh estimate for the intended scope.
Need help?
Include your step and this reference.
Vector OS guide: /tutorials/plans-and-credits
Guide updates
Understand plans and credits
Revision fbfe05954676929c3eff453ec203b4b7b53ac8eb43e65e12d338ed449921252c ·