Coconut · Rate Limits

Coconut Rate Limits

Coconut does not publish explicit numeric request-per-second or request-per-minute API rate limits in its public documentation. Throughput is instead governed by plan-level processing concurrency: the free Test Plan processes jobs sequentially (one at a time) and limits media to one minute, while paid usage runs jobs in parallel. The ultrafast setting further parallelizes a single job by splitting the input into chunks. Specific per-account concurrency ceilings are not reconciled in this artifact.

Coconut Rate Limits is the machine-readable rate-limit profile for Coconut on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring jobs and chunks.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Video, Audio, Encoding, Transcoding, and Media.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
VideoAudioEncodingTranscodingMediaRate LimitingQuotasThrottling

Limits

Test Plan Concurrency account
jobs
1 (sequential)
Free Test Plan processes jobs one at a time; input limited to one minute.
Paid Plan Concurrency account
jobs
see provider documentation
Paid usage processes jobs in parallel; specific ceiling not publicly documented.
Ultrafast Chunking job
chunks
applies to inputs longer than one minute
A single job is split into chunks for parallel transcoding when settings.ultrafast is enabled.

Policies

Asynchronous Processing
Jobs run asynchronously; rely on webhook notifications for completion instead of tight polling.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

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/coconut-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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