Skip to main content

Rate Limit Tiers

Unregistered Tier

Rate Limit: 10 requests/hour per IP Use case: Testing, personal projects, low-volume usage Requirements: None Limitations:
  • Lowest rate limit
  • IP-based tracking
  • No User-Agent required

Registered Tier

Rate Limit: 100 requests/hour Use case: Small applications, moderate usage Requirements: Valid User-Agent header Format:
Benefits:
  • 10x higher rate limit
  • Better support
  • Usage tracking

Enterprise Tier

Rate Limit: 1000+ requests/hour Use case: Production applications, high-volume usage Requirements: API key + User-Agent Benefits:
  • 100x+ higher rate limit
  • Priority support
  • Custom rate limits available
  • Usage analytics

Rate Limit Windows

Rate limits are calculated per hour (3600 seconds):
  • Window: Rolling 1-hour period
  • Reset: Continuous (not fixed hourly)
  • Tracking: Per User-Agent or API key
Example:

Cached Responses

Cached responses do not count toward rate limits. This means repeated checks of the same address won’t consume your quota.
Cache behavior:
  • Same address checked multiple times → Only first request counts
  • Different addresses → Each counts toward limit
  • Cache duration varies by endpoint

Rate Limit Headers

Every response includes rate limit information:

Header Details

Handling Rate Limits

Monitoring

Always check rate limit headers:

Exponential Backoff

When rate limited (429 status):

Caching Strategy

Implement response caching:

Best Practices

1. Use Appropriate Tier

  • Testing: Unregistered tier is fine
  • Small apps: Registered tier (add User-Agent)
  • Production: Enterprise tier (request API key)

2. Implement Caching

  • Cache responses for repeated addresses
  • Set appropriate cache TTL
  • Invalidate cache when needed

3. Monitor Usage

  • Track rate limit headers
  • Log rate limit status
  • Alert when approaching limits

4. Handle Errors Gracefully

  • Implement exponential backoff
  • Show user-friendly error messages
  • Queue requests when rate limited

5. Optimize Requests

  • Batch requests when possible
  • Use specific endpoints when appropriate
  • Avoid unnecessary requests

Upgrading Tiers

To Registered Tier

Simply add a User-Agent header:
No approval needed - automatic upgrade.

To Enterprise Tier

  1. Email [email protected]
  2. Describe your use case
  3. Provide contact information
  4. Receive API key via email

Rate Limit Exceeded Response

Status: 429 Too Many Requests Response Body:
Headers:

Fair Use Policy

Excessive requests per second may trigger stricter limits affecting all consumers. Good faith usage is expected.
Guidelines:
  • Don’t make rapid-fire requests
  • Respect rate limit headers
  • Use caching appropriately
  • Contact support for high-volume needs

Examples

JavaScript

Python