2026-06-11 22:55 UTC · openai/rate-limits · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: 21462543b2-openai-rate-limits.diff · commit 21462543b2
diff --git a/snapshots/openai/rate-limits.md b/snapshots/openai/rate-limits.mdindex ad89376..ffb8328 100644--- a/snapshots/openai/rate-limits.md+++ b/snapshots/openai/rate-limits.md@@ -23,5 +23,5 @@ Other important things worth noting: - Rate limits are defined at the organization level and at the project level, not user level. - Rate limits vary by the model being used.-- For long context models like GPT-4.1, there is a separate rate limit for long context requests. You can view these rate limits in developer console.+- For long context models like GPT-5.5, there is a separate rate limit for long context requests. You can view these rate limits in developer console. - Limits are also placed on the total amount an organization can spend on the API each month. These are also known as "usage limits". - Some model families have shared rate limits. Any models listed under a "shared limit" in your organizations limit page share a rate limit between them. For example, if the listed shared TPM is 3.5M, all calls to any model in the given "shared limit" list will count towards that 3.5M.@@ -125,5 +125,5 @@ def completion_with_backoff(**kwargs): return client.completions.create(**kwargs) -completion_with_backoff(model="gpt-4o-mini", prompt="Once upon a time,")+completion_with_backoff(model="gpt-3.5-turbo-instruct", prompt="Once upon a time,") ``` @@ -158,5 +158,5 @@ def completions_with_backoff(**kwargs): return client.completions.create(**kwargs) -completions_with_backoff(model="gpt-4o-mini", prompt="Once upon a time,")+completions_with_backoff(model="gpt-3.5-turbo-instruct", prompt="Once upon a time,") ```