Uberduck · Rate Limits

Uberduck Rate Limits

Uberduck documents tiered rate limits keyed to the subscription plan, plus a hard per-request character cap. Free-tier keys are limited to roughly 5 requests per minute and 100 per day; Pro raises this to about 60 per minute and 1,000 per day; Enterprise limits are custom. Each request accepts up to 10,000 characters of text on lower tiers (documented as up to 20,000 on Pro). Exceeding a limit returns HTTP 429 Too Many Requests, and every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers; 429 bodies include reset_at and retry_after.

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

It captures 6 rate-limit definitions, measuring requests and characters.

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

Tagged areas include AI, Text to Speech, Voice, Rate Limiting, and Quotas.

6 Limits Throttle: 429
AIText to SpeechVoiceRate LimitingQuotas

Limits

Free Tier Requests Per Minute account
requests
5 per minute
Documented free-tier per-minute request ceiling.
Free Tier Requests Per Day account
requests
100 per day
Documented free-tier per-day request ceiling.
Pro Tier Requests Per Minute account
requests
60 per minute
Documented Pro-tier per-minute request ceiling.
Pro Tier Requests Per Day account
requests
1000 per day
Documented Pro-tier per-day request ceiling.
Enterprise Requests account
requests
custom
Enterprise per-minute and per-day limits are negotiated.
Characters Per Request request
characters
10000 (up to 20000 documented on Pro)
OpenAPI TextToSpeechRequest.text maxLength is 10000; rate-limit docs cite up to 20000 on Pro.

Policies

Rate Limit Headers
Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (Unix timestamp).
429 Handling
On 429, the body includes details.reset_at (Unix timestamp) and details.retry_after (seconds); clients should back off until then.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor retry_after / X-RateLimit-Reset.

Sources