TwelveLabs · Rate Limits

Twelvelabs Rate Limits

TwelveLabs enforces per-account rate limits expressed as requests per minute on the API endpoints, plus concurrency limits on long-running indexing and embedding tasks (e.g. 25 concurrent indexing tasks on the Developer plan) and per-index volume caps (up to 10,000 hours and 100,000 videos per index). Free-plan accounts are additionally capped at 10 hours of indexing and 600 cumulative processing minutes with 90-day index retention. Enterprise limits are custom and scale with monthly spend. Specific per-endpoint RPM values are not reconciled in this artifact.

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

It captures 6 rate-limit definitions, measuring requests, tasks, hours, videos, and days.

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

Tagged areas include AI, Video Understanding, Multimodal, Search, and Embeddings.

6 Limits Throttle: 429
AIVideo UnderstandingMultimodalSearchEmbeddingsRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) account
requests
see provider documentation
Per-endpoint RPM, varies by plan.
Concurrent Indexing Tasks account
tasks
25 (Developer plan)
Maximum simultaneous video indexing tasks; higher on Enterprise.
Duration Per Index index
hours
10000 (Developer plan)
Maximum total video duration per index.
Volume Per Index index
videos
100000 (Developer plan)
Maximum number of videos per index.
Free Plan Indexing Cap account
hours
10 (Free plan)
Free accounts limited to 10 hours of indexing and 600 cumulative processing minutes.
Free Plan Index Retention index
days
90 (Free plan)
Free-plan indexes are accessible for 90 days from creation.

Policies

Tiered Limits
Limits raise as accounts move from Free to Developer (pay-as-you-go) and to Enterprise agreements with custom rate limits scaled to monthly spend.
Backoff Strategy
Clients should implement exponential backoff with jitter, honor Retry-After on 429 responses, and poll task status rather than busy-waiting.

Sources