Gero Nexus implements rate limiting to ensure fair usage and maintain service quality for all users.Documentation Index
Fetch the complete documentation index at: https://nexus.gerowallet.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Rate Limit Tiers
Rate limits vary based on your subscription plan:| Plan | Daily Limit | Per-Second Limit | Burst Limit |
|---|---|---|---|
| Free | 10,000 | 5 | 10 |
| Starter | 100,000 | 20 | 50 |
| Pro | 1,000,000 | 100 | 200 |
| Enterprise | Custom | Custom | Custom |
Burst Limit: Maximum requests allowed in a 1-second window during traffic spikes.
Rate Limit Headers
Every API response includes rate limit information in the headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Total daily requests allowed |
X-RateLimit-Remaining | Requests remaining in current period |
X-RateLimit-Reset | Unix timestamp when the limit resets |
X-RateLimit-Per-Second | Maximum requests per second |
Handling Rate Limits
Check Before Calling
Always check the rate limit headers before making additional requests:Implement Exponential Backoff
When you receive a429 Too Many Requests error, implement exponential backoff:
Best Practices
Cache Responses
Cache Responses
Cache frequently accessed data to reduce API calls:
Batch Requests
Batch Requests
Where possible, use batch endpoints to reduce API calls:
Monitor Usage
Monitor Usage
Track your API usage in the dashboard to avoid hitting limits:
- View real-time usage graphs
- Set up alerts at 80% and 90% thresholds
- Monitor per-key usage for distributed apps
Request Only What You Need
Request Only What You Need
Use field selectors to reduce response size and processing time:
Upgrading Your Plan
Need higher limits? Upgrade your plan or contact us for Enterprise custom limits.Next Steps
Error Handling
Learn how to handle API errors
Pagination
Working with paginated responses