Rate Limit
Nanonets API enforces rate limits to ensure fair usage and maintain optimal performance for all users. Getting a 429 response code from our API means that you have reached our rate-limit.
The rate limit applies to all POST requests within the OCR Predict section, including:
- Prediction for Image URL
- Prediction for Image File
- Async Prediction for Image URL
- Async Prediction for Image File
Rate Limits by Plan
Unpaid and Pay As You Go Plans:
- Custom Models:
- Initial Capacity: For the first 50 pages, the rate is set at 5 pages per minute. This allows users to handle moderate loads efficiently.
- Extended Usage: Beyond the initial 50 pages, the rate limit decreases to 2 pages per minute. This adjustment helps in managing server loads and maintaining service quality across all users.
- Instant Learning Models (IL Model):
- Initial Capacity: Like custom models, these start with a limit of 5 pages per minute for up to 50 pages, catering to typical usage scenarios.
- Extended Usage: The rate drops to 2 pages per minute after 50 pages, which balances system utilization during prolonged operations.
Pro and Enterprise Plans:
- Custom Models:
- These plans feature an enhanced rate of 20 pages per minute by default, supporting higher volume needs.
- Instant Learning Models (IL Model):
- A steady rate of 5 pages per minute is maintained.
What’s the difference between Sync Call and Async Call?
- Sync: Your files will get uploaded and processed, and you will see the results on the screen.
- Async: your files will get uploaded and processed at a later point in time (usually within 5 minutes). Recommended if you are processing a lot of large files (> 3 pages of PDFs)
You can reduce rate-limiting errors using one of these approaches:
- Handling 429 Errors
- Implement logic in your application to handle 429 (Too Many Requests) errors gracefully. This could include:
- Retrying the request after a delay.
- Exponential backoff strategies to reduce the frequency of retries.
- Alerting or logging when rate limits are approached or exceeded.
- Implement logic in your application to handle 429 (Too Many Requests) errors gracefully. This could include:
- Contact Sales team to upgrade the rate-limits
- If consistent rate limiting is impacting your application, consider contacting Sales team to upgrade the rate-limits to allows more requests.
- Reach out to us at [email protected].
Updated 4 months ago