Model limit probe

OpenAI: GPT-5 | RPM limit

OpenAI: GPT-5 RPM limit decides whether a key can enter a production route. TestKey reads model ID openai/gpt-5, provider OpenAI, catalog context, real-key headers, 429 errors, and region signals together.

Model

openai/gpt-5

OpenAI: GPT-5

Provider

OpenAI

62 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 400,000

Limit matrix summary

Model

openai/gpt-5

Limit dimension

rpm-limit

Visible signal

real key probe required

Read-only check. Detection data burns after 5 minutes.

Why this limit matters

OpenAI: GPT-5 RPM limit decides whether a key can enter a production route. TestKey reads model ID openai/gpt-5, provider OpenAI, catalog context, real-key headers, 429 errors, and region signals together.

Model: openai/gpt-5
Provider: OpenAI
Limit dimension: RPM limit

How to prove it

Read-only check. Detection data burns after 5 minutes.

Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
RPM limit must bind model ID openai/gpt-5; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 400,000

Operator action

OpenAI: GPT-5 RPM limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: real key probe required
Context window: 400,000

Open key checker

Read-only check. Detection data burns after 5 minutes.