Lightly · Rate Limits

Lightly Ai Rate Limits

Lightly does not publish explicit numeric rate limits for the LightlyOne platform REST API at https://api.lightly.ai. Practical limits are governed mainly by plan-level quotas - input dataset size (~25k samples on Community, ~100k on Team, unlimited on Enterprise) - and by concurrency of LightlyOne Worker compute runs rather than per-second request ceilings. Clients should treat the API as quota-bounded and handle HTTP 429 with backoff. Specific per-endpoint request limits are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring samples, runs, and requests.

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

Tagged areas include AI, Computer Vision, Data Curation, Active Learning, and Embeddings.

5 Limits Throttle: 429
AIComputer VisionData CurationActive LearningEmbeddingsRate LimitingQuotasThrottling

Limits

Input Dataset Size (Community) account
samples
25000
Indicative free-tier dataset quota; verify on reconciliation.
Input Dataset Size (Team) account
samples
100000
Indicative Team-tier dataset quota; verify on reconciliation.
Input Dataset Size (Enterprise) account
samples
unlimited
Enterprise removes dataset-size quotas; negotiated.
Worker Run Concurrency account
runs
see provider documentation
Concurrent LightlyOne Worker compute runs depend on registered workers and plan.
Request Rate account
requests
see provider documentation
No public numeric RPM/TPM published for the REST API; honor 429 / Retry-After.

Policies

Quota-Based Limiting
Effective limits are driven by plan-level dataset-size quotas and worker concurrency rather than published per-second request ceilings.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.

Sources