API Rate Limit Calculator

3.33 requests a second per client, one every 300 ms

Two things break a plan that looks fine as an average. Fixed windows reset on the clock rather than sliding, so firing a full allowance at the end of one window and again at the start of the next sends double the intended rate in a couple of seconds. And retries count against the quota, which means a burst of failures can consume the budget that would have let them succeed. Read the response headers instead of guessing: most APIs return the remaining count and a reset time, and honouring the Retry-After header on a 429 is more reliable than any client-side schedule.