Unverified50% confidenceFactExact time
OpenAI returns diagnostic headers on every HTTP 200 and 429 response, including x-ratelimit-remaining-requests, x-ratelimit-remaining-tokens, x-ratelimit-reset-requests and x-ratelimit-reset-tokens, with the reset headers formatted as duration strings such as 20ms or 6m0s.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/15/2026
First Seen
Valid until: 1/13/2027
Sources
Related Entities
Related Claims
UnverifiedGateway rate-limit detection typically relies on analyzing upstream response status codes; upon receiving an HTTP 429 response, it is necessary to parse information such as Retry-After or X-RateLimit-Remaining to dynamically adjust the account's available status67% similarUnverifiedAmong HTTP status codes, those starting with 2 indicate success (200 success, 201 created successfully, 204 success but no response content), those starting with 3 indicate redirection or caching (301 and 302 redirection, 304 caching), those starting with 4 indicate client errors (401 no authentication provided, 403 no permission, 422 parameter format incorrect, 429 requests too frequent), and those starting with 5 indicate internal server errors.65% similarUnverifiedSome relay providers still return HTTP 200 when the upstream rate-limits them, their balance is exhausted, or the model is unavailable, and embed the error information in the response body rather than the standard choices structure.64% similarUnverifiedOpenAI identifies refusals and max-token truncation as two scenarios in which a response may not match the schema.64% similarUnverified当API限流时会返回429状态码（Too Many Requests），通常附带Retry-After响应头指示等待时间63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1033772API
curl https://kongchang.com/api/v1/knowledge/claims/1033772MCP
get_claim(id=1033772)