# Usage


Data scanned in a month, and the monthly limit.
[Conventions](/cli/reference#conventions) apply here,
except `--quiet`: a usage report has no id, so `--quiet` is rejected as a usage
error. Use `--json` in scripts.

## Usage

Report the data scanned in a month against the monthly limit.
Usage data requires additional permissions which need to be approved by your
Account Manager.
See [Get Usage](/api/v2/usage#get-apiv2usage).

| Flag | Input |
| --- | --- |
| `--month` | a calendar month as `YYYY-MM`, from `2020-01` up to the current month in UTC, which is also the default |

Reports bytes scanned for the month, a breakdown per operation, and the
monthly limit block.

```bash
intuizi usage
intuizi usage --month 2026-08
```

For a past month, `percent_used` and `over_limit` are left empty, since they
only apply to the current month. The `limit` and `enforced` rows still show,
but they are your current limit configuration, not that month's. See
[Limits & Quotas](/concepts/limits).

The response also carries your organization's
[build budget](/concepts/limits#build-budget): the hourly and daily build
limits, the live counts, and `retry_after_seconds` once a window is used up.
The table leaves it out, so read it with `--json`. The table's `enforced` row
belongs to the data-scan limit, not the build budget.

```bash
intuizi usage --json | jq .data.build_budget
```

{{< cards >}}
  {{< card link="/developers/cli/reference/catalogs/" title="Catalogs" subtitle="Read the ids every other command needs." >}}
  {{< card link="/developers/cli/reference/webhooks/" title="Webhooks" subtitle="List registered webhook endpoints." >}}
{{< /cards >}}