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, such as your users, teams, API keys or AI agents. You choose the labels, and Limitry only matches them.

Field	Meaning
name	Your label for the limit. Unique in the workspace.
subjectKind	Which subjects it applies to: user, apikey, agent, or any kind you use.
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, cents). Used for display.
window	minute, hour, day, month, total or concurrent. See below.
rolling	With minute, hour or day: count the last 60 seconds, minutes or 24 hours. Default false.
failMode	What your code should do when Limitry can’t be reached: open (allow, the default) or closed (deny).

Windows

• minute, hour, day and month reset at UTC boundaries, unless the limit is rolling.
• total is a balance that never resets, for prepaid credits. See Pools, balances and budgets.
• concurrent allows at most amount at once. See Rolling windows and concurrency.

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

Managing limits

In the app, limits are under Settings → Limits. Owners and admins can change them, and every member can see them. Through the API, use a key or token with the limits:read or limits:write scope:

curl -X POST https://api.limitry.com/v1/limits \
  -H "Authorization: Bearer $LIMITRY_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 on the command line (limitry limits create) and the MCP server. The workspace’s audit log records every change, and a change reaches checks within a minute.