Response Analysis
Rate-Limit Header Decoder
Interpret common and provider-specific rate-limit response headers, reset times, remaining capacity, and Retry-After values locally in your browser.
Response headers
Paste the header block
Include the HTTP status line and Date header when available. Non-rate-limit fields are ignored and their values are not repeated in the results.
Interpretation
What the response says
Paste a response or use the sample, then decode its rate-limit fields.
A matching field name can be used by more than one provider. Treat these as reference matches, not provider identification.
Field-by-field result
Recognized rate-limit fields
Backed by Throttle's 57-field reference dictionary.
| Header | Raw value | Interpretation | Reference status |
|---|---|---|---|
| Decode a response to see recognized fields. | |||
Interpret conservatively
Headers describe one response, not the whole policy.
Limits can apply to a credential, route, model, resource, workspace, organization, or another provider-defined bucket. A positive remaining value does not guarantee that another request will succeed.
- 1Keep the response context
Record the status, endpoint family, credential scope, and relevant provider documentation.
- 2Read values by format
Reset fields can use epoch seconds, epoch milliseconds, durations, HTTP dates, or provider-specific forms.
- 3Honor Retry-After
Treat a valid server delay as the earliest retry time, then apply your bounded local retry policy.
- 4Expect other controls
Secondary limits, concurrency caps, abuse controls, and dynamic quotas may not appear in these fields.
Interpretation aid: Header names and meanings vary by provider and can change. Confirm critical behavior with the provider's current official documentation and the response observed by your own integration.