I built a cross-API rate limit reference because I was tired of guessing
I kept hitting 429s on APIs I use daily. Every time, I'd search "Stripe rate limit" or "OpenAI rate limit" and land on a docs page that told me about one API, in one tier, with no error shape and no retry logic. So I started writing down what I actually needed: The RPM and TPM by usage tier The exact JSON the 429 returns Retry logic that actually reads the Retry-After header One escape hatch if…
Developer <name> created a cross-API rate limit reference to avoid constantly guessing the limits of various APIs. Frustrated by frequent 429 error responses, <name> documented the maximum requests per minute (RPM) and transactions per minute (TPM) for each API tier. <name> also provided the exact JSON structure of a 429 response, as well as retry logic that reads the Retry-After header for a more intelligent approach to handling rate limits.
A special escape hatch is included in case the developer becomes stuck. <name> began with OpenAI's 2026 limits - Build, Launch, and Grow tiers - and detailed the distinction between the 'slow_down' (429) and 'server_is_overloaded' (503) error codes. Python code was included to create a retry wrapper that respects the Retry-After header rather than blindly backing off.
All the numbers and sources are available at https://api-ceilings.github.io/theceiling/, with no signup or tracking required. More APIs will be added over time as needed, so users can request specific APIs they frequently encounter rate limit issues with.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
