What is the requests-per-minute rate limit for Anthropic's latest Opus model on the lowest Claude API usage tier? Today: 1,000 requests/min. This is version 1.
https://docs.anthropic.com/en/api/rate-limits
Anthropic's official rate-limits page, https://docs.anthropic.com/en/api/rate-limits (it redirects to platform.claude.com/docs/en/api/rate-limits). The markdown copy, https://platform.claude.com/docs/en/api/rate-limits.md, shows every tier tab as plain text and is the easiest to read. If the page moves, search "Anthropic Claude API rate limits usage tier RPM".
Go to the Messages API rate-limit tables and use the table for the lowest standard tier that has published numbers. Today that is "Start" (earlier names were "Tier 1", and before that "Free"). Find the row for the newest Opus model (today "Claude Opus 5.5") and read the "Maximum requests per minute (RPM)" column. Skip the ITPM/OTPM columns, the Message Batches API RPM table, Managed Agents limits and fast-mode limits. The "Evaluation tier" for new organizations sits below Start, but the page publishes no figures for it, so it cannot be used.
Rebuilt from Wayback Machine copies of the docs page (old addresses docs.anthropic.com/claude/reference/rate-limits, docs.anthropic.com/en/api/rate-limits, docs.claude.com/..., platform.claude.com/.../rate-limits.md). 2024-04-15: Claude 3 Opus got 5 RPM on the Free tier, then the lowest tier (Build Tier 1 got 50). 2025-01-03: the Free tier was gone and Claude 3 Opus got 50 RPM on Tier 1. 2025-08-25: Opus 4.x got 50 RPM on Tier 1. 2026-06-15: Opus 4.x (4.8 and earlier) still got 50 RPM on Tier 1. Today the tiers have been renamed Start/Build/Scale, and Opus 5.5 gets 1,000 RPM on Start. The rendered HTML copies from late 2025 to mid-2026 drop the tables, so read the .md copies instead. I could not pin down the exact date of the move from 50 to 1,000 (the tier restructure). To narrow it, look at .md copies dated after 2026-06-15.
This changes only when Anthropic does something: releases a new Opus model, restructures its tiers, or changes a limit. Re-read the page every week. The value stays the same between those events.
Make sure you are on the lowest published standard tier (Start / Tier 1 / Free, depending on the era), not Build or Scale. Use the newest Opus row, not an older shared "Opus 4.x" bucket or a Fable/Mythos/Sonnet row. Read the Messages API RPM, not the Batches API RPM or fast-mode limits. The Evaluation tier has no published numbers, so do not substitute anything for it. Ignore the example figure "60 requests per minute" in the explanatory text.
Edit the text and press the button. An agent follows your version once; if the value it gets can be read in the source and is not an unexplained jump, your version goes live straight away. Otherwise it is kept in the history as not adopted, with the reason.
Sign in to improve this recipe. A free account can try three changes a day.
Sign in