Skip to main content
Rate limits are an essential part of maintaining service quality and ensuring fair usage across all users. This guide explains how rate limits work in Winnie and how to handle them effectively.

Understanding Rate Limits

Rate limits control how many requests you can make to Winnie’s API within a specific time period. These limits are based on your subscription plan and are designed to ensure optimal performance for all users.

Rate Limit Structure

  • Requests per second (RPS): Maximum number of requests you can make per second
  • Credits per month: Total number of credits available for your plan
  • Burst capacity: Short-term capacity to handle traffic spikes
  • Concurrent connections: Maximum number of simultaneous connections

Available Plans and Limits

PlanCostCreditsRequests/secAPI Keys
Free$0/month500,000101
Developer$49/month10,000,000503
Business$499/month100,000,0002005
Professional$999/month200,000,00050015
EnterpriseCustomCustomCustomCustom

Credit Usage by Method

Different API methods consume different amounts of credits:
CategoryCredit CostExample Methods
Lightweight1eth_blockNumber, net_version
Standard2eth_getBalance, eth_getCode
Heavy5eth_getLogs, debug_traceTransaction
Transaction10eth_sendRawTransaction
Archive Data20Historical data queries

Handling Rate Limit Errors

When you exceed your rate limits, you’ll receive a 429 (Too Many Requests) error:
{
  "error": {
    "code": 429,
    "message": "Rate limit exceeded",
    "details": {
      "limit": 50,
      "reset": 1647123456,
      "retry_after": 60
    }
  }
}
  1. Implement exponential backoff
  2. Monitor your usage
  3. Consider upgrading your plan
  4. Cache responses when possible

Monitoring Usage

Track your usage through the Winnie Dashboard:
  • Real-time request monitoring
  • Credit consumption tracking
  • Rate limit status
  • Usage alerts and notifications

Burst vs. Sustained Limits

  • Burst limits: Short-term capacity for handling traffic spikes
  • Sustained limits: Long-term average request rate
  • Credit system: Flexible allocation of resources

Optimization Techniques

Combine multiple requests into a single batch to reduce overhead.
Implement caching for frequently accessed data.
WebSocket connections are more efficient for real-time data.
Use exponential backoff for retrying failed requests.

Auto-scaling Options

For paid plans, Winnie offers auto-scaling capabilities:
  • Automatic credit top-up
  • Burst capacity allocation
  • Dynamic rate limit adjustment
  • Usage-based scaling

Common Issues

Check your current usage and plan limits. Consider implementing better request throttling.
Monitor your credit usage and implement caching strategies.
Implement proper request queuing and backoff strategies.

Response Headers

Winnie includes helpful headers in responses:
HeaderDescription
X-RateLimit-LimitYour plan’s rate limit
X-RateLimit-RemainingRemaining requests in current window
X-RateLimit-ResetTime until rate limit resets
X-Credits-RemainingRemaining credits for the month