Rate Limits
CleverThis applies rate limits at multiple levels: workspace-level limits set by the plan tier, namespace-level limits configured by workspace administrators, and provider-level limits enforced by upstream LLM providers.
When a rate limit is hit, CleverThis returns 429 Too Many Requests with a Retry-After header.
Plan tier limits
These are the default workspace-level limits per plan. Administrators can request limit increases.
| Limit | Starter | Pro | Enterprise |
|---|---|---|---|
| Requests per minute (all namespaces) | 60 | 600 | Custom |
| Tokens per minute (all namespaces) | 100,000 | 1,000,000 | Custom |
| Namespaces | 3 | 20 | Unlimited |
| API keys | 10 | 100 | Unlimited |
| Actor deployments | 5 | 50 | Unlimited |
Namespace-level limits
Workspace administrators can set per-endpoint rate limits that are more restrictive than the workspace limit. For example, a dev namespace might be capped at 10 RPM to prevent runaway test scripts from consuming budget. See Managing Endpoints for how to configure these.
Provider-level limits
Each upstream LLM provider (OpenAI, Anthropic, etc.) has its own rate limits. CleverThis proxies these limits transparently — if an upstream provider returns a rate limit error, CleverThis returns a 429 to the caller with an upstream_rate_limited error code. These limits are determined by your provider account tier, not by CleverThis.
Rate limit headers
All responses from the inference API include rate limit headers:
| Header | Description |
|---|---|
X-RateLimit-Limit-Requests | Max requests per minute |
X-RateLimit-Remaining-Requests | Remaining requests in current window |
X-RateLimit-Limit-Tokens | Max tokens per minute |
X-RateLimit-Remaining-Tokens | Remaining tokens in current window |
X-RateLimit-Reset-Requests | Timestamp when request limit resets (Unix epoch) |
Burst allowances (short-lived spikes above the steady-state limit) and rate limit configuration via the API are being added.