Limit changes

Claude Opus 5.5 added with separate rate limits

Detected September 23, 2026, 05:15 UTC · Claude API rate limits

Previously, only Opus 5 held an independent quota apart from the combined Opus 4.x pool, and fast mode limits applied only to Opus 5 and 4.8. Claude Opus 5.5 now receives its own standalone rate limit and dedicated fast mode limits.

This documentation page defines API throughput thresholds across the Claude model families. Previously, usage for Opus editions 4.5, 4.6, 4.7, and 4.8 counted toward a single shared traffic ceiling, whereas version 5 maintained its own separate allocation. In addition, experimental accelerated execution settings were restricted to version 5 and version 4.8, each governed by isolated throughput caps.

The revised rules incorporate Claude Opus 5.5 into this operational framework. Under the updated policy, version 5.5 is assigned an individual quota that operates independently of the shared legacy collection and distinct from version 5. Furthermore, callers invoking accelerated execution on version 5.5 are routed to distinct speed-oriented limits rather than drawing from baseline allowances.

In practical terms, organizations adopting version 5.5 will not impact their existing bandwidth for earlier Opus variants, and overages on rapid-speed calls will trigger standard temporary block codes accompanied by cooldown indicators. However, the documentation excerpt does not disclose the precise numerical values for version 5.5 limits, such as specific minute-by-minute token volumes or concurrency maximums across account tiers, leaving exact quantitative capacity unspecified.

We compare this page once a day and record every difference. The text above is written by Claude Network from that comparison; none of it is copied from the source.

Source: Claude API rate limits