Weglot Rate Limits
The primary usage constraint on the Weglot API is the per-plan translated-word allowance (and the included number of languages), not a published per-second request rate. Word allowance is consumed as unique content is translated, and a project that exceeds its plan allowance stops translating new content (or auto-upgrades to the next tier when enabled). Weglot does not publish explicit per-minute / per-second request quotas for the translate or public endpoints; specific request-rate values are not reconciled in this artifact.
Weglot Rate Limits is the machine-readable rate-limit profile for Weglot on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring words, languages, and requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Translation, Localization, Internationalization, Machine Translation, and Multilingual.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/weglot-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.