Quota & limits

Quota keeps workspace usage predictable. Pegasus applies both daily credit limits and plan caps such as bot count and document storage.

Subscription overview with plan and daily credit context

Daily credit pool#

Credits are the daily quota units Pegasus shows for chat, training, widget, and API-style usage.

What consumes credits#

• Chat messages and assistant responses.
• Training work that embeds document chunks.
• Widget visitor conversations.
• API/PAT conversations.

Daily reset#

Credits reset at 00:00 UTC every day. The Subscription page shows the remaining amount and reset countdown.

Shared pool across chat and training#

Both chat and training consume credits from the same daily pool. If you trained a large bot earlier in the day, your chat budget for the rest of the day is reduced.

Why usage cost varies#

There is no flat per-message price. The final cost depends on:

• Model used - advanced models cost more.
• Document context size - long documents pull more chunks into the prompt.
• Max Mode - multiplies the cost about 5-7x per message vs Standard RAG.
• Output length - longer answers cost more.
• Retrieved knowledge snippets and other prompt context.

For billable actions, Pegasus may reserve an initial credit before calling downstream AI systems. After the real token usage is known, the system can top up or roll back the reservation.

Daily credit limit#

The bottom of the left sidebar shows live credit remaining: " / credits". A small badge on the Subscription page shows the same. When you cross 80%, an inline warning appears in the chat input.

When daily credits are exhausted, chat, widget, API, or training actions can be blocked until the UTC reset.

Typical message: "Daily limit reached" or "Daily credit limit reached. Cannot train now. Resets at midnight UTC."

Chat can also show:

You have used all credits for today. Resets at UTC.

or:

Daily credit limit reached. Resets at midnight UTC.

→ Fix path: Daily credit limit reached

Daily limits by plan#

The only way to raise your daily limit is to upgrade your plan.

When the limit does not apply#

• For teams where quota tracking is disabled by workspace policy - the credit counter does not increment.
• This is rare and not a way to get more credits as a regular user.

Bot count limit#

Each plan has a maximum active bot count. If you hit it, the create button may be disabled and Pegasus explains the cap.

→ Fix path: Bot limit reached

Document storage limit#

Each bot has a document storage cap. Uploading a file can fail if the file would exceed the bot's limit.

→ Fix path: Document storage limit reached

Team read-only and quota-disabled states#

Team workspaces can also enter read-only or quota-disabled states. In those states, write actions may be paused even if individual users still have visible plan information.

Workspace billing context#

The Subscription page is scoped to the active workspace. Switch workspaces before interpreting quota, plan, or feature gates.

Personal workspace#

In Personal context, Subscription describes your own plan:

• Workspace type: Personal.
• Your daily credits.
• Your bot and document limits.
• Your API/Max Mode access.

Team workspace#

In Team context, Subscription describes the team entitlement:

• Workspace type: Team.
• Team name.
• Your role.
• Your seat.
• Read-only or quota-disabled state if present.

If an action works in Personal but fails in Team, check the team subscription and seat first. The reverse can also happen: a team may unlock a capability your personal workspace does not include.

→ Fix path: Team workspace is read-only