Fern · Rate Limits

Fern Api Rate Limits

Fern does not publish fixed numeric HTTP rate limits for its hosted Ask Fern REST API. Practical usage is governed by plan-based AI credits rather than a per-minute request cap - the Hobby tier includes 250 AI credits per month and the Team tier 1,000, with Enterprise negotiated. SDK generation and docs generation run through the open-source `fern` CLI, so their throughput is bounded by your own CI/CD and local compute rather than by a Fern-imposed limit. Publishing generated SDKs is ultimately subject to the rate limits of the downstream registries (npm, PyPI, Maven) and of GitHub.

Fern Api Rate Limits is the machine-readable rate-limit profile for Fern on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, credits, runs, and publishes.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include SDK Generation, API Documentation, Developer Tools, Rate Limiting, and Quotas.

4 Limits Throttle: 429
SDK GenerationAPI DocumentationDeveloper ToolsRate LimitingQuotas

Limits

Ask Fern API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the hosted Ask Fern REST API.
AI Credits account
credits
per plan (Hobby 250/mo, Team 1000/mo, Enterprise custom)
AI-powered features (Ask Fern) consume monthly AI credits that vary by plan tier.
CLI Generation Throughput deployment
runs
compute-bound
SDK and docs generation run via the open-source CLI, bounded by your own CI/local compute.
SDK Publishing registry
publishes
downstream
Publishing generated SDKs is subject to npm, PyPI, Maven, and GitHub rate limits, not Fern's.

Policies

Credit-Based Metering
AI documentation features are metered by monthly AI credits per plan rather than by request-rate caps.
Backoff Strategy
Clients of the Ask Fern API should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources