> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Companion usage and limits

> Understand monthly Companion usage, the notices above the composer, and what happens when Companion is paused or switches to less capable models.

Companion usage is counted per month for your billing organization. Read this page when a usage notice appears above the Companion composer, or when Companion stops answering because a limit was reached.

> [!NOTE]
>
> Companion prices and limits are managed in [**Settings → Billing**](https://platform.open.cx/settings/billing). Changing limits requires the **Billing** Write permission. For how Companion usage is priced, see [Billing](https://docs.open.cx/billing.md#companion-usage).

## How usage is counted

* Usage in linked organizations counts toward the main billing organization's Companion usage.
* Usage resets on the 1st of each month (UTC).
* Usage can lag by a few minutes, so it can go slightly past a limit.

## What happens at the limit

> [tab] Without a Companion price
>
> Your main billing organization has a free monthly Companion allowance, shown in **Plan** as **Companion usage · Free tier (Fair usage)**. When it's used up, Companion keeps working with all its tools, but it uses less capable models until the month ends, so answers to complex questions may be less thorough. Companion never pauses on the free allowance.
>
> A notice appears from 30% of the allowance. To get more Companion usage, contact the OpenCX team.

> [tab] With a Companion price
>
> Companion keeps working past its included usage, and the extra usage is billed, unless your organization set limits with **Set limits** on the Companion price:
>
> * **Switch to less capable models at**: Companion keeps working on less capable models until the month ends.
> * **Stop Companion at**: new Companion messages are refused until the month ends.
>
> A notice appears from 80% of the next limit, and while either limit is in effect. Without limits, no notice appears.

## Usage notices in Companion

A notice sits above the composer on the Companion page and in the floating panel.

| Notice | What it means |
| - | - |
| **This organization has used N% of this month's Companion usage.** | The free allowance is partly used. |
| **This organization has used N% of its Companion usage before Companion switches to less capable models** (or **pauses for the rest of the month**) | Your organization is nearing a limit it set. |
| **This organization has used this month's Companion usage.** | The free allowance is used up. Companion uses less capable models until the month ends. |
| **This organization reached the limit it set for Companion, so Companion uses less capable models until** the reset date | Your switch limit is in effect. |
| **Companion is paused until** the reset date **because this organization reached the Companion limit it set for this month.** | Your stop limit is in effect. |

Select **Learn more** for an explanation. Members with **Billing** Read in the main billing organization see amounts there; everyone else sees the percent used.

Dismiss a notice with its ✕. It comes back at 50%, 80% and 100%, and again next month. Dismissing is remembered in your browser only. The paused notice can't be dismissed.

## When Companion is paused

While the stop limit is in effect:

* Starting a chat or sending a message shows the paused message instead of a reply, on the Companion page, in the floating panel and from ⌘K.
* Tasks Companion was already running finish.
* Published mini apps keep working, and past chats stay readable.

Companion resumes on the 1st of next month. To resume sooner, an admin with **Billing** Write raises or removes **Stop Companion at** in **Settings → Billing**; the change takes effect right away.

## See how your team uses Companion

**Reports & Apps → Companion adoption** shows active teammates against seats, sessions and turns, what teammates use Companion for, and escalations to the OpenCX team. It requires the **Reports** Read permission.

## Companion under a partner brand

When your organization uses a partner's branding with an app name, the sidebar item and the label at the top of the Companion page read **‹app name›'s agent** instead of **Companion**. The floating bar (**Ask Companion…**), usage notices and permissions keep the name Companion. See [Partner branding](https://docs.open.cx/partners/branding.md).

***

## Related Documentation

> [card] [Billing](https://docs.open.cx/billing.md#companion-usage)
>
> Companion prices, allowance and limits.

> [card] [Companion introduction](https://docs.open.cx/companion/introduction.md)
>
> What Companion does and who can use it.

> [card] [Partner branding](https://docs.open.cx/partners/branding.md)
>
> Your app name across the dashboard.

> [card] [Permissions reference](https://docs.open.cx/security/permissions-reference.md)
>
> Billing, Reports and Companion permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.