Limits

Cosmo Realtime uses a two-tier cap system: soft caps that trigger warnings, and hard caps that block new sessions once reached.

Soft caps

A soft cap is a configurable threshold you set in the dashboard. When accumulated usage crosses a soft cap:

• The dashboard shows a warning banner.
• An email notification is sent to the workspace billing contact.
• Existing sessions are not interrupted.
• New sessions continue to start normally.

Soft caps are advisory. Use them to catch unexpected spikes before they affect your bill.

Hard caps

A hard cap is an absolute ceiling enforced by the server. When usage reaches a hard cap:

• New POST /session/start calls return 503 Service Unavailable.
• Existing active sessions are not interrupted — in-flight sessions run to completion.
• The error response body indicates a capacity limit was reached.

Hard caps reset at the start of each billing period.

What happens at 503

{
  "detail": "Workspace has reached its realtime session limit for this period."
}

The SDK surfaces this as a session_start_failed error. Your application should:

1. Check the dashboard to determine which limit was reached.
2. Adjust your soft-cap alert thresholds.
3. Contact support if you need a higher hard cap for your plan.

Configuring limits

Soft caps are configurable per-workspace in the dashboard under Settings → Limits. Hard caps are set at the plan level and require a support request to change.

[Screenshot placeholder: Limits settings page showing voice-minutes soft cap and tool-dispatches soft cap input fields]

Specific values

Specific limit values are not documented here because they vary by plan and are subject to change. See the Settings → Limits page in your dashboard for the current values for your workspace.