Spending limits
Cap spending per app, per key, or for the entire team before requests reach providers.
Spending limits stop runaway integrations before they bill you. They are evaluated by the gateway before any provider call, so a request that would exceed a limit is rejected without spending credits.
Where to set limits
- Team-level — set under Settings → Limits. Caps the team's total spend over a window.
- Per-app — set on a specific OAuth app under Settings → Apps → [app] → Settings.
- Per-key — set when you create or edit an API key under Settings → API keys.
A request must satisfy every applicable limit to succeed. The most restrictive limit always wins.
Choosing windows
Limits typically apply over a window such as daily, weekly, or monthly. Pick a window that matches your billing rhythm. Daily limits are useful for surfaces with bursty traffic; monthly limits are common for steady-state production apps.
What happens when a limit is hit
The gateway returns an error indicating which limit was exceeded. Your client should treat this as a hard failure for that request — retrying without raising the limit will not help. You can raise or remove the limit from the same page where it was set.
Recommended setup
- Start with a monthly team limit slightly above your expected spend.
- Add per-app limits for any app shipped to customers, even internal ones.
- Add per-key limits for keys used in scripts or short-lived environments.