Meters, tiers, invoices
Billing
Billing is usage-based on top of a tier subscription. Three meters: tokens (in and out, priced per model family), tool time (agent runs, per second of external tool execution), and storage (graph plus files, per GB-month). Prices per family are on each model page; the meters are the same everywhere.
Tiers
| tier | base | includes |
|---|---|---|
| Free | $0 | Sandbox plus low production limits; embeddings free up to 1M tokens/mo |
| Pro | $49/mo | Pro rate limits, 10 GB storage, email support |
| Scale | $499/mo | Scale limits, 100 GB, fine-tuning preview, priority support |
| Enterprise | custom | Everything in /docs/enterprise |
Controls
- Hard monthly spend cap — runs fail with budget_exceeded rather than overspend
- usage.threshold webhooks at any percentage you set
- Per-key spend attribution in the usage API — cost per service, not just per project
- max_steps is also a cost ceiling: a halted run bills only the steps it took
Invoices and credits
Invoices issue on the 1st, itemized by meter and model family, with usage CSV attached. Failed deep runs caused by 5xx errors are auto-credited — you can see the credits line on the invoice. Annual prepay carries a 15% discount on Pro and Scale.