Skip to main content
The Knouds API enforces rate limits per user, per route, per 60-second window. Limits are tied to your tier, independent of which capabilities your key carries. When you exceed the limit, requests return 429 until the current window resets.

Per-tier limits

Free tier has no API key access — the table is shown for completeness only. Pro+ unlocks key creation.
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 from a rate-limited endpoint includes three headers that reflect the state of your current bucket:
You can inspect these headers with curl -i:

429 responses

When you exceed the limit, the API returns HTTP 429 with the RATE_LIMIT_EXCEEDED code:
The response also includes the standard rate limit headers plus a Retry-After header (in seconds) indicating exactly how long to wait before retrying:
Check X-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.
If your workload consistently hits rate limit walls, upgrading your tier raises your quota — from 100 req/min on Pro to 1,000 req/min on Business, or unlimited on Enterprise.