A faulty loop in your application can trigger a lot of model calls in a short time. So that this doesn't catch you off guard, there are two tools: the spending limit, which stops at a fixed amount per month, and warning thresholds, which notify you in good time. You set up both under Billing.
Monthly spend limit
The spending limit applies to your whole team, so to all keys combined, and to the current calendar month.
- Open Billing in the dashboard.
- In the Monthly spend limit box, enter the amount under Limit in euro, with at most two decimal places.
- Click Save limit.

Above the field, you can see how much has already been used this month, for example "Used this month: €0.63 of €20.00." Running calls are already counted with their reservation.
Once the limit is reached, the API rejects further calls until the month changes or you raise the limit. Your application then gets HTTP 429 with a code such as spend_limit_exceeded.
- Leave the field empty: No limit applies.
- Enter 0: No more calls are possible. This is handy if you want to stop the API completely for a while without revoking any keys.
You can also give each individual key its own monthly limit, see Create API keys: permission, limit and validity. Whichever limit is reached first always applies.
Warning thresholds
Warning thresholds don't stop anything, they only notify you. There are two lists with at most 10 amounts each:
- Available amount falls below: You get a warning when your available credit (minus reservations) falls below the amount. If it later rises above it again, for example through a top-up, the same threshold warns you again the next time it's crossed.
- Monthly spend reaches: You get a warning when the billed usage of the current calendar month reaches the amount. Each threshold fires once per month.
Here's how to set them up:
- Click Add amount in the appropriate list.
- Enter the amount in euros, for example
20.00. - Repeat this for other amounts. The cross removes an amount again.
- Click Save warning thresholds.
We notify you by email, in the app and by webhook with the credit.threshold event, if you've set up a webhook for it. Set up FlowModels webhooks shows how.
Who gets the warnings
Recipients lists all people who receive the warnings by email: the team owner and people with a managing role in the team who have access to FlowModels. You control who belongs to this group via Team in the FlowModels sidebar.
If something goes wrong
- "Enter a euro amount above 0 with at most two decimal places.": Warning thresholds must be greater than 0.
- "This amount is already in the list.": Each amount can appear only once per list.
- Topping up doesn't help: Once the spending limit is reached, a top-up doesn't change that. Raise the limit or wait until the month changes.
- No warning received: Check whether an address is listed under Recipients. If it says "There is currently no address that can receive warnings.", nobody can be warned by email.