Camb.AI · Rate Limits

Camb Ai Rate Limits

Camb.AI does not publish fixed numeric per-minute request limits for the API. Consumption is governed primarily by the monthly credit allowance of the subscription plan - credits are spent across TTS, dubbing, translation, and transcription - together with per-plan ceilings such as characters per generation, custom voice count, video file size, concurrent teams, and live streaming minutes and concurrent streams. Because most operations are asynchronous (create a task, then poll), the documentation recommends polling status endpoints at reasonable intervals (roughly every 5 to 15 seconds) rather than tight loops.

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

It captures 6 rate-limit definitions, measuring credits, characters, voices, bytes, and minutes.

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

Tagged areas include AI, Text to Speech, Dubbing, Translation, and Rate Limiting.

6 Limits Throttle: 429
AIText to SpeechDubbingTranslationRate LimitingQuotas

Limits

Monthly Credit Allowance account
credits
per plan (2000 Free to 1.8M Expert)
Shared credit budget consumed across all products; the primary consumption control.
Characters per Generation request
characters
per plan (for example 3000 on Essentials/Pro; unlimited on higher tiers)
Streaming TTS accepts 3 to 3000 characters per request on lower tiers.
Custom Voices account
voices
per plan (1 Free to 150+ Expert)
Ceiling on the number of stored custom (cloned or designed) voices.
Video File Size request
bytes
per plan (for example up to 1 GB on Premier and above)
Applies to dubbing and other media uploads.
Live Streaming account
minutes
per plan (for example 15 minutes, 1 concurrent stream on Expert)
Realtime streaming minutes and concurrent stream count are plan-gated.
API Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented.

Policies

Polling Interval
Poll asynchronous task status endpoints at reasonable intervals (about 5 to 15 seconds) until status is SUCCESS, rather than in a tight loop.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Credit Metering
Requests consume plan credits; streaming TTS surfaces the cost via the X-Credits-Required response header.

Sources