Creatify · Rate Limits

Creatify Rate Limits

Creatify does not publish fixed numeric per-minute request rate limits for the API. In practice, throughput is governed by two things: (1) your subscription's monthly credit allowance, which caps how much video/audio you can generate, and (2) the asynchronous nature of generation - each create call enqueues a job that renders in the background, so callers create a job then poll GET /{resource}/{id}/ (or wait for a webhook) rather than blocking. Callers should poll on a reasonable interval and back off on 429 responses.

Creatify Rate Limits is the machine-readable rate-limit profile for Creatify on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, credits, jobs, and characters.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI Avatars, Video Generation, Marketing Video, Rate Limiting, and Quotas.

4 Limits Throttle: 429
AI AvatarsVideo GenerationMarketing VideoRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented for the Creatify API.
Monthly Credit Allowance account
credits
per plan
Generation is capped by the plan's monthly credit allowance (e.g. API Starter 500, API Pro 2000).
Concurrent Render Jobs account
jobs
not published
Concurrency of background render jobs is not documented; Enterprise accounts may negotiate higher throughput.
Text-to-Speech Script Length request
characters
8000
The text_to_speech script field is capped at 8000 characters per request.

Policies

Asynchronous Generation
Media endpoints return a job with a status immediately; clients poll GET /{resource}/{id}/ until status is "done" or supply a webhook_url to be notified.
Credit Metering
Throughput is bounded by credits consumed (roughly 5 credits per 30s of video, 1 credit per 30s of audio) rather than by a request-per-second cap.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses, and poll job status on a reasonable interval rather than tight-looping.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/creatify-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.