skip to main content
Browse documentation

Limits & alerts

Put hard ceilings on spend and traffic, and get notified before a usage meter runs out.

Limits & alerts (/limits) is one page with three tabs: the Budget tab holds spend caps, the Traffic tab holds rate limits, and the Alerts tab holds usage alarms. Caps and rate limits enforce — they block when a ceiling is reached. Alarms notify — they alert configured channels without blocking. All three are enforced server-side. The page replaces the three separate pages these controls used to have; the old links redirect to it.

Spend caps

Spend caps, on the Budget tab, set a hard spending ceiling per scope and period. Alerts fire at the percentages you configure; the hard cap blocks further requests once it is reached.

  • Scope and period — cap by workspace, user, or conversation, over a daily, monthly, or per-conversation window.
  • Hard cap — a ceiling in USD; requests are blocked when spend reaches it.
  • Alert thresholds — a ladder of percentages, each firing an alert as spend climbs toward the cap.

Rate limits

Rate limits, on the Traffic tab, throttle traffic per scope. A soft limit warns; a hard limit blocks.

  • Scope — limit by workspace, tenant, tool, user, or IP address, optionally targeting a specific value.
  • Soft and hard limits — the soft limit warns, the hard limit blocks further requests.
  • Window — the number of requests allowed per rolling time window, in seconds.

Usage alarms

Usage alarms, on the Alerts tab, notify you before a meter runs out. An alarm fires when this month’s usage crosses a threshold percentage of your plan allowance — it alerts, it does not block. Every workspace starts with alarms at 85% and 100%.

  • Threshold — the percentage of your monthly usage-credit allowance at which the alarm fires.
  • Channels — notify by email, Slack, or webhook.
  • Defaults — the seeded 85% and 100% alarms can be edited, disabled, or deleted, and you can add your own.

Next steps