Overview
Electron Hub implements rate limiting to ensure fair usage and maintain service quality for all users. Rate limits are measured in Requests Per Minute (RPM) and vary by subscription plan.You can check your current rate limits and usage anytime in the API Keys section of your dashboard.
Rate Limit Tiers
| Subscription Plan | Requests per minute (RPM) | Best For |
|---|---|---|
| Free | 5 RPM | Testing and prototypes |
| Starter | 10 RPM | Small applications |
| Plus | 15 RPM | Growing projects |
| Core | 20 RPM | Professional use |
| Pro | 30 RPM | Production applications |
| Business | 60 RPM | High-volume usage |
| Enterprise | 100+ RPM | Custom enterprise needs |
How Rate Limiting Works
Request Counting
- Each API call counts as one request regardless of model or complexity
- Both successful and failed requests count toward your limit
- Streaming requests count as a single request when initiated
Time Windows
- Rate limits are calculated using a sliding window of 60 seconds
- If you exceed your limit, you’ll receive a
429error - The limit resets continuously, not at fixed intervals
- Important: When you exceed your rate limit, there’s a 3-minute cooldown period before you can make requests again
Cooldown Period: If you exceed your rate limit, you must wait 3 minutes (180 seconds) before making any new requests. This cooldown is enforced even if your normal rate limit window would have reset.
Rate Limit Headers
Every API response includes headers showing your current status:Handling Rate Limits
Error Responses
When you encounter rate limits, you’ll receive different error codes depending on the type of limit: Rate Limit Exceeded (429)Special Model Limits
Some models have additional daily limits beyond the standard rate limits:Google Models (Daily Limits)
Google experimental and preview models have daily usage limits that reset at 21:00 UTC:| Subscription Plan | Daily Requests | Models Affected |
|---|---|---|
| Free | 50 | Experimental/Preview models only |
| Starter | 50 | Experimental/Preview models only |
| Plus | 75 | Experimental/Preview models only |
| Core | 100 | Experimental/Preview models only |
| Pro | 150 | Experimental/Preview models only |
| Business | 300 | Experimental/Preview models only |
| Enterprise | 500 | Experimental/Preview models only |
Experimental/Preview models include models with
-exp or -preview in their names, such as:gemini-1.5-flash-expgemini-2.0-flash-expgemini-2.0-flash-thinking-exp-1219gemini-2.5-flash-preview-05-20gemini-2.5-pro-preview-05-06
gemini-1.5-flash, gemini-1.5-pro, gemma-3-27b-it) are not subject to these daily limits.Midjourney Models (Daily Limits)
Midjourney image generation has a separate daily limit:- Daily Limit: 50 requests per day
- Reset Time: 21:00 UTC
- Applies to: All Midjourney image generation endpoints
Implementing Retry Logic
Request Queuing
For applications with variable load, implement a request queue:Optimization Strategies
1. Batch Processing
Group multiple operations when possible:2. Efficient Model Selection
Choose the right model for your task:- GPT-3.5-turbo: Fast and cost-effective for simple tasks
- GPT-4o: Best for complex reasoning and analysis
- Claude-3-haiku: Fastest for quick responses
- Claude-3-5-sonnet: Balanced performance and capability
3. Request Optimization
Optimize your requests to reduce unnecessary calls:4. Caching Results
Cache responses for repeated queries:Monitoring Usage
Check Current Usage
Monitor your API usage programmatically:Dashboard Monitoring
Use the dashboard to:- View real-time usage statistics
- Set up usage alerts
- Monitor trends over time
- Identify peak usage periods
Upgrading Your Plan
When to Upgrade
Consider upgrading when you:- Consistently hit rate limits
- Need higher throughput for production
- Want to reduce latency from queuing
- Require dedicated support
How to Upgrade
- Visit your dashboard
- Go to “Billing”
- Select your desired plan
- Complete the upgrade process
- New limits take effect immediately
Best Practices
Implement Graceful Degradation
Implement Graceful Degradation
Design your application to handle rate limits gracefully:
- Show loading states during retries
- Provide fallback responses when possible
- Queue non-urgent requests for later processing
- Inform users about temporary delays
Monitor and Alert
Monitor and Alert
Set up monitoring for rate limit issues:
- Track 429 error rates
- Alert when approaching limits
- Monitor request patterns
- Analyze peak usage times
Optimize Request Patterns
Optimize Request Patterns
Structure your requests efficiently:
- Batch similar operations
- Use appropriate models for tasks
- Cache common responses
- Implement smart retry logic
Plan for Growth
Plan for Growth
Prepare for scaling:
- Start with higher limits before launch
- Monitor usage trends
- Have upgrade path ready
- Consider enterprise plans for large scale
