docs(knowledge-base): API rate limits on the rate limits page - #255
Merged
Merged
Conversation
…scopes, bursts and the 429 shape The rate limits page described limits as per API key with no numbers. The request rate limiter counts units per minute per organization, pod and inbox; this page now states the cost classes (1/2/4/8), the budgets per plan, how bursts work, and the 429 body and headers the API returns, and points pollers at webhooks and WebSockets. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… and remedies Drop the unit costs, per-plan budgets, scope shares and burst mechanics: publishing the exact numbers tells an abusive client how to stay just under them. The page now says what the limit is for, that it is generous and absorbs bursts, what a 429 looks like, how to avoid it, and that higher plans raise it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
duharry0915
changed the title
sidharth0612
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The request rate limiter goes to
enforcein production. The rate limits page said limits were "per API key" and nothing else, so a customer receiving the new429had nothing useful to read.What changed
One file,
fern/pages/knowledge-base/rate-limits.mdx. The page deliberately does not publish the limiter's internals (unit costs, per-plan budgets, per-inbox and per-pod shares, burst sizes): exact numbers tell an abusive client how to stay just under them. It says:429looks like (Retry-After, usually 1 s;messageandfixin the body) and that the SDKs retry it automatically, with a retry helper for direct callers;Retry-After;The sending-limits table and the existing tips are unchanged.
Not verified
The TypeScript SDK's retry behaviour was checked in 0.5.19 (
requestWithRetries: 408 / 429 / 5xx, honorsRetry-After); the Python SDK was not checked separately. No local Fern build; the preview workflow on this PR renders it.🤖 Generated with Claude Code