Limits are spend ceilings you set ahead of time, so a runaway integration or a spike in usage can never surprise you on the bill. They come in two levels:
- API key limits — cap what a single Mizan key can spend, on top of any project it belongs to.
- Project limits — cap what an entire project can spend, combining every key inside it.
Each limit has two independent forms you can set on their own or together: a lifetime cap (total spend, ever) and a rolling period cap (spend within a window you choose, e.g. every 30 days, resetting automatically). The moment either one is hit, every further call on that key — or, for a project limit, on any key in that project — is rejected with a 403 until the limit is raised, cleared, or its period rolls over.
Limits only gate platform-routed (wallet-billed) calls. A BYOK call served by a provider account you've connected never touches Mizan's spend, so it isn't counted or blocked by any limit here.