OpenRouter spending cap: Yes
Does OpenRouter have a hard spending cap?
Yes Per the docs as of Oct 19, 2026: OpenRouter runs on prepaid credits, and every API key can have its own credit limit in USD (a lifetime cap, or one that resets daily, weekly or monthly). Once a key uses its limit, its requests are rejected.
How do I turn on a spending limit in OpenRouter?
- Add credits on the Credits page. If you turn on auto top-up, remember a key with no limit can spend those top-ups too.
- Create (or edit) an API key and set a Credit limit under Key limit in the key dialog.
- Pick a reset interval (daily, weekly or monthly, resetting at midnight UTC) or leave it unset for a lifetime cap.
- If you use your own provider keys through OpenRouter (BYOK), switch on Include BYOK usage in limit, or that traffic never counts toward the cap.
- Give each app or agent its own key with its own limit.
What happens when the OpenRouter limit is hit?
Per the docs, requests on that key fail with 403 Forbidden and a Key limit exceeded message until the window resets or you raise the limit. If the account balance runs out, requests fail with 402.
Gotchas
- Docs: “A key with no limit lets a leaked key or a runaway agent spend your entire balance, including any auto top-ups.”
- BYOK spend is not counted toward a key's limit unless you turn on include_byok_in_limit (default is off).
- Workspace-wide budgets are an Enterprise plan feature; per-key credit limits are available on every plan.
- Keys created for you during onboarding get a $100 credit limit and expire after 180 days.
- Credits may be expired after one year per OpenRouter's terms, and refunds of unused credits are only accepted within 24 hours of purchase.