Monthly, weekly, and daily caps with reset anchors.
Rate rules handle bursts; quotas handle budgets. Attach a long-window cap to a namespace and Brume enforces it alongside the rate rule, with billing-cycle-aware resets.
Monthly, weekly, and daily caps with reset anchors.
Rate rules handle bursts. Quotas handle budgets. A quota caps how much an identifier can consume over a long window — an hour, a day, a week, a month — regardless of how politely the traffic is spread out.
A rule of 100 requests/minute says nothing about how many requests arrive in a month. A user who stays under the per-minute limit every minute can still burn through a shared resource, an expensive downstream API, or your margin. Quotas are the second axis:
Both are enforced inside the same atomic evaluation. A request must pass both.
| Field | Values | Meaning |
|---|---|---|
period | hourly · daily · weekly · monthly | The quota window |
anchor_mode | first_call · billing_date | When the window resets |
billing_day | 1–28 | With billing_date: the day of month the window resets |
first_call starts each identifier's window on its first evaluation — simple and fair. billing_date aligns every identifier's window to a calendar boundary — what you want when the quota mirrors a billing cycle.
success: false, with the quota's reset time.check() reports quota usage without consuming it.PLAN_LIMIT (rate_limit_quotas_cap_reached).GET /v1/ratelimit/quotas — listPOST /v1/ratelimit/quotas — createDELETE /v1/ratelimit/quotas/:id — removeQuotas require the manage_project scope.