# Usage and billing visibility

> See usage, limits, and invoices; the backend stays the quota authority.

Usage and limit figures shown in the CLI and the control plane are advisory. The Yalla backend is the authority that enforces quotas and produces invoices.

## Check usage

```bash
yalla usage --org <org-id>
```

Add `--json` to read the same numbers as a stable [Yalla envelope](/docs/api-envelopes) instead of formatted text.

## Limits and quotas

When a quota is exceeded the API answers with a stable code such as `E_RATE_LIMITED` — branch on the [error code](/docs/error-codes), not the message, and retry only when the catalog marks it safe.

## Invoices

Invoices and plan details live in the billing section of the control plane. Public documentation never shows account-specific amounts or payment details.

> [!NOTE]
> If usage looks wrong, capture the `request_id` from the usage response and [escalate to support](/docs/support) — never guess at corrections.
