Mediastack Rate Limits
Mediastack enforces a monthly-quota model rather than a published per-second TPS limit. Each subscription plan ships an included monthly request count; requests beyond that count are either billed as overage (paid plans) or hard-rejected with `usage_limit_reached` (Free plan). Limits are scoped per access_key. Mediastack does not publicly document a per-second or per-minute throttle; bursty clients should self-throttle and use exponential backoff if HTTP 429 is returned.
Mediastack Rate Limits is the machine-readable rate-limit profile for Mediastack on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 8 rate-limit definitions, measuring requests_per_month, items_per_response, and feature_gate.
The profile also includes 5 backoff/retry policies defined and response codes documented for invalidAccessKey, functionAccessRestricted, quotaExceeded, and serverError.
Tagged areas include Rate Limiting, News, Quota, and Apilayer.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.