Creatomate Rate Limits
Creatomate's primary throughput constraint is the rendering concurrency and monthly credit pool tied to each subscription plan rather than published per-second request limits. Renders are queued and processed asynchronously, so high request volumes are absorbed by the render queue; the binding limits are the included credits per month and the number of renders that can be processed in parallel. Specific per-plan concurrency and any HTTP request rate limits are not enumerated in this artifact.
Creatomate Rate Limits is the machine-readable rate-limit profile for Creatomate on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring renders, credits, and requests.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Media, Video Generation, Image Generation, Automation, and Templates.
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.