The balance
Your organization has one balance, denominated in US dollars. Every agent it owns draws from the same balance.CLI
Topping up
Add funds through a hosted checkout session with the payments provider. You can also set up a subscription that grants a monthly dollar allowance.How usage is metered
Costs are measured against vendor invoices, not list price, and drawn from the balance in real dollars. What you see quoted is what you are charged — see the rate card.- Model calls — per token across five tiers, at the completion window tariff.
- Computer — per second while running; paused meters storage only; no creation fee.
- Priced tools —
web_search/web_fetchper call,generate_image/generate_videoper finished job.
- Quoted before the call and checked against your budget and balance.
- Recorded as an idempotent ledger entry — the balance can never be double-charged for the same call.
- Floored at zero — the wallet never goes negative; a small post-hoc overshoot is forgiven rather than clawed back.
Reading spend
CLI
session_id, and the acting actor, so spend is attributable end to end.
Vetta meters against measured vendor cost because list-price rate cards over-state real cost by 1.017x–4.176x depending on harness and window — see Benchmarks.
Attribution & live usage
- Who spent it — every action and money movement is principal-attributed; see the audit log.
- Live cost per run — a session exposes
consumed_micro_usdand 5-tiertoken_usage, and emitssession.usagebefore idle. See Observability.
On the wire
Money is integer micro-USD (_micro_usd, 1 USD = 1_000_000) everywhere on the wire — every ledger entry, session consumed_micro_usd, and quote. The CLI renders dollars for humans.
Next: pricing & the completion window
How the window changes what you pay.