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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/lightly-ai-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.