Rate limiting

Rate-limit behavior is deployment- and route-dependent. The current API documentation does not establish a universal customer tier table or guaranteed header contract, so clients must not hard-code values from older drafts.

On throttling, honor any documented retry indication, apply bounded exponential backoff with jitter, and avoid request storms. If the response does not provide a retry indication, stop and retry conservatively rather than guessing a reset time.

For persistent throttling, record the route family, environment, timestamps, and redacted response and contact Support.