Limits

A limit says how much of an action a subject may use per window — for example, every user may generate-image 10 times per day. Subjects are whoever acts in your product: your users, teams, API keys or AI agents. You choose the labels; Limitry attaches no meaning to them beyond matching.

Field	Meaning
name	Your label for the limit; unique in the workspace.
subjectKind	Which subjects it applies to (user, apikey, agent …).
subjectId	One subject, or empty for every subject of that kind.
action	The action it limits, or * for every action.
amount	How many units per window.
unit	What the amount counts (images, credits …) — for display.
window	minute, hour, day or month — fixed windows that reset at UTC boundaries; total: a balance that never resets (Pools, balances and budgets); concurrent: at most amount at once (Rolling windows and concurrency).
rolling	With minute, hour or day: count the last window at the moment of the check instead of the calendar one. Default false.
failMode	What your code should do when Limitry can’t be reached: open (allow, the default) or closed (deny).

When several limits match a subject and action, all of them apply.

Managing limits

In the app: Settings → Limits (owners and admins change them; every member can see them). Through the API, with a key or token holding the limits:read / limits:write scopes:

curl -X POST https://api.limitry.com/v1/limits \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Daily images","subjectKind":"user","action":"generate-image","amount":10,"unit":"images","window":"day"}'

The same operations are in the command line (limitry limits create …) and available to agents through the MCP server. Every change is in the workspace’s audit log.

Limits are enforced by checks.