Unbabel Rate Limits
Unbabel does not publish fixed numeric rate limits for the Translation API (tapi/v2) in its public developer documentation. Because translation is an asynchronous, enterprise, quote-based service, throughput is governed in practice by the customer's contracted translation volume/commitment rather than by a documented per-second or per-minute request cap. Submitting a translation returns immediately with a job uid; clients then poll the translation/{uid} endpoint or receive a callback, so polling should be reasonable and backed off rather than tight-looped.
Unbabel Rate Limits is the machine-readable rate-limit profile for Unbabel on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and words.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Translation, LangOps, Rate Limiting, and Quotas.
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/unbabel-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.