Introduction

Limitry is the runtime that decides whether a request is allowed. When your product is about to do something that costs — call a model, run a job, spend credits, open another connection — it asks Limitry one question: may this subject do this, at this cost? Limitry answers in milliseconds, and keeps everything behind the answer: counters and resets, rolling windows, reservations, shared credit pools, budgets, concurrency and entitlements.

• Subjects are whoever acts in your product: a user, a workspace, a service, an API key — or an AI agent.
• A check is the question; the answer is allowed or not allowed, with what remains and why.
• Built for agents as well as people. Every operation is available through the API, the command line and the MCP server, so an agent can set Limitry up in your codebase and ask before doing anything that needs a person (Approvals).

Start with limits — the rules — and checks — the question your code asks.