Quota & limits

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

Subscription page with your plan and the Daily credits card

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 reads and indexes documents.
• Widget visitor conversations.
• API/PAT conversations.

Daily refill#

Credits refill at 00:00 UTC every day. Pegasus shows that moment in your local time: the Daily credits card on the Subscription page says "Credits refill in {hours}h {minutes}m, at {time}."

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 - uses roughly 5-7 times the credits of a standard answer.
• 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 Daily credits box at the bottom of the left sidebar shows the credits left today as "{remaining} / {total} credits". The Daily credits card on the Subscription page shows Used, Remaining, and Daily limit.

When daily credits run out, chat, widget, API, and training requests are blocked until the refill:

• In chat, one notice above the message box says "Daily credit limit reached. Credits refill today at {time}." (or "tomorrow at {time}") with a View subscription button.
• The sidebar box shows "Credits refill at {time}."
• The Subscription page shows "You've used today's credits" with the refill time, and See plans when a higher plan is available.

All of these times are in your local time.

→ Fix path: Daily credit limit reached

Daily limits by plan#

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

Usage paused for a team#

When credit usage is paused for a team, the Daily credits card shows Paused and "Credit usage is paused for this team. Chats and bots stay readable; contact your team owner to resume." The team is read-only until usage resumes; see Read-only state.

Bot count limit#

Each plan has a maximum number of bots you can own. When you reach it, Create new chatbot is disabled and the reason appears next to it.

→ 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 paused usage#

Team workspaces can also become read-only or have their usage paused. In those states, changes are paused even though plan information stays visible.

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:

• "Personal workspace" under the plan name.
• Your daily credits.
• Your bot and document limits.
• Your Max Mode, API, and document reader access.
• The Plans comparison and your billing history.

Team workspace#

In Team context, Subscription describes the team's plan:

• The team name, your role, and your seat under the plan name.
• The team's status, such as Active, Cancelling, or Usage paused.
• The team's daily credits, limits, and features.

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