Fern Rate Limits
Fern's customer-facing limits are expressed as plan-level metering rather than per-second HTTP rate limits. Public Fern surfaces — the docs site, dashboard, and the fern-mcp-server hosted endpoint — do not document per-request rate limits on their public pages, so this file captures the consumption metering that does exist (seats and AI credits) plus generic safe-harbor guidance for programmatic consumers.
Fern 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 5 rate-limit definitions, across the hobby, team, and enterprise tiers, measuring seats and ai_credits_per_month.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include AI, API Definitions, Code Generation, Developer Experience, and Documentation.
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.