Cleanlab · Rate Limits

Cleanlab Rate Limits

Cleanlab applies per-account rate limits to its hosted APIs - the Trustworthy Language Model (TLM), Codex validation, and Cleanlab Studio inference. TLM enforces concurrency and request-rate limits that vary by tier (free vs. paid). The Python clients retry transient errors and respect rate limiting. Specific per-tier numeric limits are not consistently published and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring concurrent_requests and requests.

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

Tagged areas include AI, LLM, Trustworthiness, Data Quality, and Guardrails.

4 Limits Throttle: 429
AILLMTrustworthinessData QualityGuardrailsRate LimitingQuotasThrottling

Limits

TLM Concurrent Requests account
concurrent_requests
see provider documentation
Maximum in-flight TLM requests; varies by free vs. paid tier.
TLM Requests Per Minute account
requests
see provider documentation
Per-account TLM request rate; varies by tier.
Codex Validation Requests project
requests
see provider documentation
Per-project validate request rate.
Studio Inference Requests account
requests
see provider documentation
Per-account deployed-model prediction request rate.

Policies

Tiered Limits
Limits raise as accounts move from free to paid usage and via Enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After; the official Python clients retry transient errors automatically.

Sources