Rate limit docs should show the 429 response and retry pattern

An API documentation note about scope, headers, retry-after behavior, and safer alternatives to repeated polling.

A rate limit page should do more than name the number. Developers need the scope, the window, headers, 429 body, retry-after behavior, and a safe retry pattern. If webhooks, exports, or batch endpoints reduce request volume, those alternatives should appear next to the limit instead of being buried elsewhere.