Run a localisation platform from an agent or CI
One company's docs show a full fit.
What counts as done
Sources uploaded, pre-translation or a job started, translations downloaded into the right paths, and any failure surfaced as a non-zero exit or error the agent can act on, with rate limits handled by retries.
How agents ask for it: push the new strings to Crowdin
, pull the latest translations before deploy
, what's still untranslated in Spanish
, pre-translate the new keys
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
Does the job, with a limit 6
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Crowdin BB Crowdin OÜ | CLI, API and MCP upload sources, pre-translate and download builds. The first-hand report of a failed download exiting 0 is closed as completed (September 2026), but 429s above 20 concurrent requests carry no Retry-After. source |
| Lingo.dev B Replexica, Inc. | lingo push submits a server-side run and exits, and lingo pull re-attaches and writes results, with a CI guide, but exit codes and 429 retry behaviour are not documented on the page read. source |
| Localazy C Localazy s.r.o. | API and CLI import sources and fetch translations, with rate limits of 10 requests a second and daily import and fetch caps per plan, but no 429 retry guidance or CLI exit-code docs were found. source |
| Lokalise BB Lokalise, Inc. | Upload queues an import process, async download returns a process to poll for the bundle, and the CLI wraps both, but an open report shows frequent 429s with a request for built-in backoff. source |
| Phrase B Phrase a.s. | Strings and TMS APIs, the CLI and a hosted MCP push and pull translations, but CLI exit codes on failure and 429 retry guidance were not read today. source |
| POEditor MCP server E Code Whale Inc. | Project upload, sync, export (a download URL), translation status and untranslated lists are tools on the hosted server, but tool error behaviour is undocumented and the API drops queued requests past the plan's limit. source |
Doesn't do this job 9
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Amazon Translate BB Amazon Web Services, Inc. | A translation engine, not a localisation platform; no project, upload or pull workflow. |
| Azure Translator BB Microsoft Corporation | A translation API, not a localisation platform. |
| DeepL API BB DeepL SE | A translation API and CLI, not a localisation platform with projects to push and pull. |
| Google Cloud Translation BB Google LLC | A translation API, not a localisation platform. |
| Lara Translate API B Translated s.r.l. | Lara CLI translates files in a repository but is not a TMS with projects to push to and pull from. source |
| LibreTranslate D LibreTranslate | A translation server, not a localisation platform. |
| Lingvanex Translation API F Nordicwise Limited | A translation API, not a localisation platform. |
| SYSTRAN Translate API E SYSTRAN SAS | A translation API, not a localisation platform. |
| TranslatePlus E PetaBytes, Inc. | A translation API, not a localisation platform. |
What stops agents finishing
- failed download exits 0 so the release ships untranslated
- 429 with no retry guidance mid-job
- sync step deletes target-only keys on every run
Around it
Before: code.read-repo, translation.localise-app-strings. After: code.open-pull-request, infrastructure.deploy.
Where this comes from
Weight 6 of 100 in Translation: 3 of 55 accounts (exit 0 on failure, 429 on async download, sync deleting plurals); vendors' MCP pitches carry the rest
The same as data: /api/v1/use-cases/translation.sync-tms.json, or the MCP tool get_use_case with id translation.sync-tms. Other jobs in this category: /api/v1/niches?category=translation.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.