Lingo.dev · Rate Limits

Lingo Dev Rate Limits

The Lingo.dev Localization Engine is metered primarily by translated-word volume tied to the account's plan allotment rather than by published per-minute request quotas. Requests are authenticated with an organization-scoped X-API-Key; exhausting the plan's monthly word allotment moves usage into metered overage (or is blocked on the free tier). Specific per-minute request and concurrency limits are not publicly reconciled in this artifact.

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

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

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

Tagged areas include AI, Localization, Translation, i18n, and Developer Tools.

3 Limits Throttle: 429
AILocalizationTranslationi18nDeveloper ToolsRate LimitingQuotasThrottling

Limits

Monthly Translated Words account
words
per plan allotment
10,000 (Hobby), 20,000 (Pro), 100,000 (Team); overage metered per 1,000 words above allotment.
Requests Per Minute (RPM) account
requests
see provider documentation
Per-account request rate; not publicly published as a fixed value.
Concurrent Jobs account
jobs
see provider documentation
Asynchronous job groups run one durable background job per target locale.

Policies

Word-Volume Metering
Usage is metered against the plan's monthly translated-word allotment, then billed as overage.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 / Retry-After responses.
Asynchronous Offload
Large multi-locale workloads should use the async jobs API so work runs as durable platform workflows that survive restarts.

Sources