Klu · Rate Limits

Klu Ai Rate Limits

Klu does not publish explicit numeric rate limits for the Klu Engine API in its public documentation. Generation throughput is effectively bounded by the upstream LLM provider limits (OpenAI, Anthropic, and others) tied to the keys connected to a workspace, and by any account-level limits Klu applies to Action runs. Specific per-account or per-endpoint values are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and tokens.

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

Tagged areas include AI, LLM, LLM App Platform, Rate Limiting, and Quotas.

3 Limits Throttle: 429
AILLMLLM App PlatformRate LimitingQuotasThrottling

Limits

Action Runs account
requests
see provider documentation
No published numeric limit on POST /v1/actions; bounded by account and upstream provider limits.
Upstream Model Tokens account
tokens
see upstream provider documentation
Token throughput is governed by the connected LLM provider's rate limits for the workspace key.
Context Ingestion account
requests
see provider documentation
Document and file ingestion into Context libraries; no published numeric limit.

Policies

Upstream Pass-Through
Generation limits largely follow the rate limits of the upstream LLM provider connected to the workspace.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 / Retry-After responses.

Sources