> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/organization-administration/billing.md).

# Billing and usage

Billing belongs to the selected organization. Open the organization menu and choose **Billing and usage** before checking allowances or changing a plan. Prices and products are retrieved dynamically; use the current plan dialog and checkout for the amount and terms that apply to your organization.

## Review your allowance

1. Check **Your plan** for the organization’s subscription and member allowance.
2. Review billing-cycle token usage and any warning about approaching or exceeding the allowance.
3. Use the usage-period selector to inspect the period relevant to your investigation.
4. Compare the selected reporting period with the billing cycle before interpreting the totals.

A usage report is not an invoice, and an empty or unavailable value is not proof of zero usage. If the subscription cannot be loaded, resolve that error before assuming tools are available.

Member allowances also affect [team invitations](https://docs.katara.ai/about/organization-administration/members.md). Other limits can apply to data sources, collections, publishing frequency, and agent entitlements. Do not infer that a plan name alone enables every feature: current backend subscription capabilities are authoritative.

## Manage the plan

Choose **Manage your plan** to open the current catalog and available plan-management actions. Review the selected product and checkout terms before confirming a paid change. Complete any payment setup requested by the application, then return to Billing and usage and verify the resulting subscription.

Where offered for a finite plan, the **pay-as-you-go** control changes how additional usage is handled. Review the displayed terms before enabling it. It does not grant missing content permissions, remove all service limits, or enable an unavailable runtime feature.

## When an operation is blocked

The dashboard can block protected tools when subscription status is unknown or invalid, and can request setup when a payment method is missing. Backend admission also checks conditions such as inactive subscriptions, exceeded usage, failed payment methods, past-due status, and stale billing periods. Not every backend condition has an identical dashboard screen.

Check the selected organization, subscription state, usage allowance, and payment setup first. If those are correct, check [resource access](https://docs.katara.ai/about/organization-administration/access.md) and [feature availability](https://docs.katara.ai/about/reference/availability.md): permission failures and disabled Brain services are not necessarily billing problems.

For support, retain the organization ID, affected operation, error message, and reporting period. Do not send payment-card details or API secrets. A successful checkout or accepted request is not by itself confirmation that the original operation completed; verify its result separately.
