Fred Rate Limits
FRED enforces a single, published per-key rate limit: 120 requests per minute. The limit applies equally to the FRED API and the GeoFRED Maps API (the same api_key is used by both). There are no separate live / sandbox modes, no concurrency caps, and no per-IP throttle published. Consumers that exceed the limit receive a temporary rejection; FRED recommends staying well inside the cap by batching requests, caching responses, and backing off on errors. Heavy users (warehouse syncs, mirror builds) are encouraged to download the bulk data files published on the FRED website rather than scraping the API.
Fred Rate Limits is the machine-readable rate-limit profile for FRED on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring requests_per_minute, concurrent_requests, and varies.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.
Tagged areas include Rate Limiting, Finance, Government, and Economic Data.
generated, dated 2026-05-28.
Limits
Policies
Sources
- https://fred.stlouisfed.org/docs/api/api_key.html
- https://fred.stlouisfed.org/docs/api/fred/overview.html
- https://fred.stlouisfed.org/legal/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.