Autocontent Api Rate Limits
Published throttling for AutoContent API. The limits that exist are commercial — a daily asset cap and a concurrency cap attached to each legacy plan — plus a handful of per-route limits on the legacy API. What is NOT published is the runtime signal: neither surface returns a RateLimit-* or X-RateLimit-* header, so a client can only discover it has hit a limit by receiving a 429.
Autocontent Api Rate Limits is the machine-readable rate-limit profile for AutoContent API on the APIs.io network, in the API Commons Rate Limits shape.
It captures 9 rate-limit definitions, across the amateur, professional, enterprise, all, and none tiers, measuring assets, concurrent_requests, interval, and requests.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Artificial Intelligence, Audio, Content Generation, Podcasts, and Video.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.