The Knouds API enforces rate limits per user, per route, per 60-second window. Limits are tied to your API key’s scope. When you exceed the limit, requests returnDocumentation Index
Fetch the complete documentation index at: https://docs.knouds.ai/llms.txt
Use this file to discover all available pages before exploring further.
429 until the current window resets.
Limits by scope
| Scope | Plan tier | Limit |
|---|---|---|
free | Free | 10 requests/min |
deployment | Pro | 100 requests/min |
admin | Business / Enterprise | 1,000 requests/min |
super_admin (platform administrators) have no rate limit applied.
Rate limits are tracked independently per route. Calls to POST /api/workflows/:slug/run and POST /api/models/:internalName/run each maintain their own bucket — calls to one do not consume quota on the other.
Rate limit headers
Every successful response includes three headers that reflect the state of your current bucket:| Header | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests allowed per window for your scope |
X-RateLimit-Remaining | Requests remaining in the current 60-second window |
X-RateLimit-Reset | Unix epoch second at which the current window resets and your quota refills |
curl -i:
When you are rate limited — 429
When you exceed the limit, the API returns HTTP429 with the RATE_LIMIT_EXCEEDED code:
Retry-After header (in seconds) indicating exactly how long to wait before retrying:
Recommended back-off pattern
CheckX-RateLimit-Remaining before dispatching batch calls. If the value falls below 5, pause and wait until X-RateLimit-Reset before sending more requests. When you receive a 429, read the Retry-After value and sleep for that many seconds before retrying.