FlowModels

Budgets and limits: what applies per key and what applies to the whole team

Published on 11. November 2026

FlowModels has several limits that are easy to mix up. Some apply to a single key, others to your whole team. Here you can see them at a glance. Whichever limit is reached first always applies.

The limits at a glance

Limit Applies to Where to set it Error when reached
Monthly limit of the key one key API keys → Edit 429 spend_limit_exceeded
Monthly spend limit all of the team's keys Billing 429 spend_limit_exceeded
Credit (prepaid) or credit line (postpaid) the whole team Billing 429 insufficient_quota
Requests per minute team, can be set lower per key API keys → Edit 429 rate_limit_exceeded
Concurrent requests the whole team determined by the tier 429 concurrent_requests_exceeded

Budget here always means euros, request limit means the number of calls. Euro amounts are checked before the call: open reservations of running requests count too, and a rejected call costs nothing.

Per key

You set the monthly limit when you create or edit a key, as a whole euro amount from 1 to 100,000, see Create API keys. Without an entry, the key has no limit of its own. This lets you ring-fence a test system or a customer, for example.

You can also lower the per-minute request limit per key, but never beyond the team limit. The details are in Edit, renew or revoke API keys.

For the whole team

You set up the monthly spending limit and warning thresholds under Billing, see Set up a spending limit and warning thresholds. The tier determines the requests per minute and the concurrent requests of the whole team, see Request limit: how the tiers work.

All euro limits refer to the current calendar month and start over when the month changes.

For end users of your application

There is no separate budget and no separate limit for individual end users. If you want to limit your customers, do so in your application, for example based on the costs from GET /v1/usage with group_by=end_user, see Analyze usage via API. Or give each customer their own key with its own monthly limit.

Which limit is stopping you right now

  • 429 insufficient_quota or credit_balance_exhausted: Add credit. Raising the spending limit doesn't help here.
  • 429 spend_limit_exceeded or period_spend_limit_exceeded: The monthly limit of the key or the team has been reached. A top-up doesn't help. Raise the limit or wait until the month changes.
  • 429 rate_limit_exceeded and 429 concurrent_requests_exceeded: Wait the number of seconds given in Retry-After.

More on the codes in Understanding FlowModels error messages. Your application can fetch the current values with GET /v1/key and GET /v1/credits, see Check credit and key limits via API.

Was this article helpful?

Back to Credit & billing