klingai-rate-limits

Featured

Handle Kling AI API rate limits with backoff and queuing strategies. Use when hitting 429 errors or planning high-volume workflows. Trigger with phrases like 'klingai rate limit', 'kling ai 429', 'klingai throttle', 'kling api limits'.

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Kling AI Rate Limits ## Overview Kling AI enforces rate limits per API key. When exceeded, the API returns `429 Too Many Requests`. This skill covers detection, backoff strategies, request queuing, and concurrent job management. ## Rate Limit Tiers | Tier | Concurrent Tasks | Requests/Min | Notes | |------|------------------|-------------|-------| | Free | 1 | 10 | 66 daily credits cap | | Standard | 3 | 30 | Per API key | | Pro | 5 | 60 | Per API key | | Enterprise | 10+ | Custom | Contact sales | ## Exponential Backoff with Jitter ```python import time, random, requests def exponential_backoff(attempt: int, base: float = 1.0, max_wait: float = 60.0) -> float: """Calculate wait time with jitter to avoid thundering herd.""" wait = min(base * (2 ** attempt), max_wait) jitter = random.uniform(0, wait * 0.5) return wait + jitter def request_with_retry(method, url, headers, json=None, max_retries=5): for attempt in range(max_retries + 1): response = method(url, headers=headers, json=json, timeout=30) if response.status_code == 429: if attempt == max_retries: raise RuntimeError("Rate limit: max retries exceeded") wait = exponential_backoff(attempt) print(f"429 rate limited. Waiting {wait:.1f}s (attempt {attempt + 1})") time.sleep(wait) continue if response.status_code >= 500: if attempt == max_retries: response.raise_for_st...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

castai-rate-limits

Handle CAST AI API rate limits with backoff and request queuing. Use when hitting 429 errors, optimizing API call patterns, or implementing rate-aware batch operations. Trigger with phrases like "cast ai rate limit", "cast ai 429", "cast ai throttle", "cast ai API limits".

2,266 Updated today
jeremylongshore
AI & Automation Featured

klingai-known-pitfalls

Avoid common mistakes when using Kling AI API. Use when troubleshooting or learning best practices. Trigger with phrases like 'klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices'.

2,266 Updated today
jeremylongshore
AI & Automation Featured

klingai-common-errors

Diagnose and fix common Kling AI API errors. Use when troubleshooting failed video generation or API issues. Trigger with phrases like 'kling ai error', 'klingai not working', 'fix klingai', 'klingai failed'.

2,266 Updated today
jeremylongshore
AI & Automation Featured

klingai-job-monitoring

Track and monitor Kling AI video generation task status. Use when building dashboards, tracking batch jobs, or debugging stuck tasks. Trigger with phrases like 'klingai job status', 'kling ai monitor', 'track klingai task', 'klingai progress'.

2,266 Updated today
jeremylongshore
AI & Automation Featured

klaviyo-rate-limits

Implement Klaviyo rate limiting, backoff, and request queuing patterns. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Klaviyo. Trigger with phrases like "klaviyo rate limit", "klaviyo throttling", "klaviyo 429", "klaviyo retry", "klaviyo backoff", "klaviyo Retry-After".

2,266 Updated today
jeremylongshore