Plans and capacity

Two things determine what a plan costs: how much of the platform you have set up, and how much you use it.

What a plan caps

Capacity limits apply to the things that exist rather than the things that happen:

• Active agents
• Active skills
• Active knowledge stores, and the amount of material in them
• Active toolkits
• Active members
• Active conversations

Hitting a cap refuses the creation rather than silently degrading. Skills and knowledge stores are the two people usually meet first, and both have a straightforward answer: remove what is no longer used, or move plan.

Current usage against every cap is on the Usage screen.

What consumes credits

Consumption follows activity, principally voice sessions and their length, chat volume, report generation, and signal processing across sessions.

The breakdown by source is the number to look at. It answers where spend is actually going, which is what you would change if you wanted a different bill. A month heavy on report generation and light on voice looks nothing like the reverse, and the totals alone will not tell you which you are having.

Reading it

The usage screen holds credit history, consumption by source, and a by-year view for the longer picture. The plan itself is managed from the same place, including moving between plans and reaching the billing portal for invoices and payment details.

Planning capacity

Two rules of thumb.

Agents multiply usage rather than adding to it: each published agent attached to an entity is a route into voice sessions, and voice is the heaviest consumer. Adding a second agent to the same team usually costs more than adding a second knowledge store.

Unused configuration still counts against caps. Draft agents, superseded skills and abandoned knowledge stores occupy capacity, and clearing them out is the cheapest way to make room.