Overview
RunAgent implements rate limiting to ensure fair usage and platform stability. Rate limits apply per API key and vary by subscription tier.Rate Limit Tiers
Tier | Requests/Hour | Requests/Minute | Concurrent Requests |
---|---|---|---|
Free | 100 | 10 | 2 |
Pro | 1,000 | 100 | 10 |
Team | 5,000 | 500 | 25 |
Enterprise | Custom | Custom | Custom |
Rate Limit Headers
Every API response includes rate limit information:Header | Description |
---|---|
X-RateLimit-Limit | Maximum requests allowed |
X-RateLimit-Remaining | Requests remaining in window |
X-RateLimit-Reset | Unix timestamp when limit resets |
X-RateLimit-Reset-After | Seconds until limit resets |
Rate Limit Response
When rate limited, you’ll receive a 429 response:Handling Rate Limits
Exponential Backoff
Rate Limit Aware Client
Quota Types
API Request Quotas
Standard rate limits for API calls:- Invoke endpoint: Standard rate limits apply
- Stream endpoint: Counts as single request
- Health endpoint: Not rate limited
Token Quotas
Monthly token usage limits:Tier | Tokens/Month |
---|---|
Free | 100,000 |
Pro | 2,000,000 |
Team | 10,000,000 |
Enterprise | Custom |
Concurrent Request Limits
Maximum simultaneous requests:Monitoring Usage
Check Current Usage
Usage Alerts
Set up alerts when approaching limits:Best Practices
1. Implement Retry Logic
2. Batch Requests
3. Cache Responses
4. Use Webhooks
Instead of polling:Rate Limit Increases
Need higher limits? Options:- Upgrade Plan: Move to higher tier
- Request Increase: Contact support for custom limits
- Enterprise Plan: Fully customizable limits
See Also
- Authentication - API authentication
- Error Handling - Rate limit errors
- Best Practices - Optimization tips