FEATURED GUIDE · 7 MIN READ
How to Handle HTTP 429 Responses
A practical guide to Retry-After, rate-limit headers, bounded backoff, jitter, queues, and safe retry behavior.
Read the guideAPI LIMITS · PERFORMANCE · RESILIENCE
Throttle gives developers practical tools for understanding API limits, handling failures, measuring performance, and designing applications that keep moving.
EXPLORE THROTTLE
WORK WITH REAL NUMBERS
Estimate expected request load, safety-adjusted capacity, remaining headroom, and queue time.
Open tool → Retry PlanningGenerate bounded exponential-backoff schedules with Retry-After handling, jitter ranges, cumulative wait time, and code templates.
Open tool → Response AnalysisInterpret common and provider-specific rate-limit response headers, reset times, remaining capacity, and Retry-After values locally in your browser.
Open tool → Payload AnalysisMeasure UTF-8 bytes, JSON minification savings, character counts, and estimated transfer volume locally in your browser.
Open tool →Throttle calculators perform their work locally and do not send workload values to an API.
SOURCE-BACKED REFERENCES
| Service | Primary limit | Authentication | Last verified | Open |
|---|---|---|---|---|
| GitHub API | 5,000 requests per hour for most authenticated users | Optional for public resources | → | |
| Stripe API | 100 requests per second globally in live mode | API key or OAuth for Connect | → | |
| OpenAI API | Varies by model, project, and usage tier | API key | → | |
| Anthropic API | Varies by model and usage tier | API key | → | |
| Discord API | 50 requests per second globally for bots and users | Bot token, OAuth, or webhook token | → |
FEATURED GUIDE · 7 MIN READ
A practical guide to Retry-After, rate-limit headers, bounded backoff, jitter, queues, and safe retry behavior.
Read the guidePLAN BEFORE THE LIMIT
Estimate capacity, add a safety margin, and find out when work needs a queue.