# Usage, cost and limits

> What was spent, today's ceilings and when they reset, and how to read the usage breakdown.

`vibiz_usage` (or `GET /v1/usage`, `vibiz usage`): what was spent in a period (`24h`, `7d`, `30d`, `month`; group by `tool`, `model`, `project`, `api_key`, `end_user`, `day`…) and today's limits:

- `credits` (prepaid accounts): `balance_cents` and `status`; at `payment_required` paid calls answer `402`, see `vibiz_billing`.
- `daily_spend`: `spent_usd`, `held_usd` (reserved by calls in flight), `limit_usd` (the account's daily safety cap, $5 by default, raisable by the owner), `remaining_usd`. It resets at `resets_at` (midnight UTC); the `24h` period is a rolling window, so it can differ slightly from the calendar day.
- `projects`: used / limit (10 by default). `builds_today`: per project, used / limit (30 a day). `ai_budgets` and `email_today` (50 a day): per project, when set or used.
- breakdown rows: `billed_usd` (what you are charged), `cost_usd`, `units` (tokens, calls, …).

Payments fees are not spend: they come off the payment itself (`vibiz_payments get` → `fees`).

Check it before costly work (AI, actions, many builds) and tell the user when `remaining_usd` is low.