Core Concepts
Understand the fundamental concepts of Limitry
Events
Events represent individual usage occurrences in your application. Each event tracks:
- Customer identifier
- Event type (e.g.,
model_call,embedding) - Token counts
- Costs
- Custom properties
Quotas
Quotas define usage limits for customers. They can be:
- Hard limits: Block requests when exceeded
- Soft limits: Allow requests but send alerts
- Dimension-based: Filtered by properties (user_id, team_id, etc.)
Rate Limits
Rate limits control request frequency, preventing abuse and ensuring fair usage.
Customers
Customers represent your end users or tenants. Each customer has their own usage tracking and limits.
Time Windows
Quotas and rate limits operate within time windows (hourly, daily, monthly, etc.).
Next Steps
- Tracking Usage - Learn how to track events
- Setting Quotas - Configure limits
- API Reference - Explore the full API