Translate with fixed terms and names
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Every glossary term appears in the output as specified, for regional variants such as EN-GB and pt-BR, on text and document calls, and the agent can add, change and list entries through the API.
How agents ask for it: keep our product names in English
, use our glossary for this
, always translate 'buyer' as 'acheteur'
, update the glossary with these terms
Does the job, with a limit 13
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 |
|---|---|
| Amazon Translate BB Amazon Web Services, Inc. | Custom terminology (CSV, TSV or TMX, up to 30 targets) applies on TranslateText and batch jobs, one file per request, but entries are changed by re-importing the file rather than edited one by one. source |
| Azure Translator BB Microsoft Corporation | Document translation takes a glossary file and LLM translation takes reference translations or an adaptive dataset, but text calls have no glossary list to add, change and remove entries through the API. source |
| Crowdin BB Crowdin OÜ | The API and the MCP glossaries tool set create, edit and remove glossaries, terms and concepts, but whether MT and AI pre-translation enforce every term per regional variant was not documented on the pages read. source |
| DeepL API BB DeepL SE | v3 glossaries are created, edited and deleted by API and apply to text and documents, up to 5 per request, but must use root codes (EN, PT) for all variants, and open reports show a client library not applying the glossary. source |
| Google Cloud Translation BB Google LLC | Unidirectional and equivalent-term glossaries (TSV, CSV, TMX) apply on v3 text and documents, but updating means replacing all entries from a new file through glossary.patch, and stopwords bypass glossary entries. source |
| Lara Translate API B Translated s.r.l. | Unidirectional and multidirectional glossaries (CSV or TBX) with regional codes like en-US and fr-FR apply per call by gls_ id, but entry-level edits were not confirmed; the MCP glossary-listing schema failure (acc-29) is closed. source |
| Lingo.dev B Replexica, Inc. | Glossaries hold terms with source locale (or any), target locale, type and hint, applied by the engine on every call, but whether terms are added and edited through the public API was not confirmed on the page read. source |
| Localazy C Localazy s.r.o. | Glossary terms are listed, created, updated and deleted through the API with translateTerm, caseSensitive and exactMatch flags, and AI translation considers the glossary, but enforcement per regional variant is not documented and the endpoint is beta. source |
| Lokalise BB Lokalise, Inc. | Glossary terms are created, updated, listed and deleted through the API, but whether automatic_translation tasks enforce every term per regional variant was not documented on the pages read. source |
| Phrase B Phrase a.s. | termBasesConfig enforces term bases on v2 text and file translations, with regional codes like es_419, but only with an AI translation agent profile, and term base editing sits in the TMS API, not read today. source |
| POEditor MCP server E Code Whale Inc. | Glossary tools list, add, update and delete terms and translations, with CSV import and export and do-not-translate terms, but whether automatic translation enforces glossary terms is not stated. source |
| Smartcat D Smartcat Platform Inc. | Glossaries are part of projects and translation profiles, but glossary entry management through the API was not found in the guides read. source |
| SYSTRAN Translate API E SYSTRAN SAS | User dictionaries take entry add, update and delete calls and apply through a profile UUID on text and file calls, but per-variant behaviour is not documented and withDictionary is deprecated. source |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| LibreTranslate D LibreTranslate | No glossary or terminology parameter; a first-hand report shows a term translated literally in both directions. source |
| Lingvanex Translation API F Nordicwise Limited | No glossary or terminology parameter in the spec. source |
| TranslatePlus E PetaBytes, Inc. | No glossary or terminology parameter in the OpenAPI spec. source |
What stops agents finishing
- glossary not available for the regional variant the agent must use
- glossary ignored by a client library or document call
- entries cannot be edited, so the glossary must be rebuilt
- MCP glossary tools fail output schema validation in the client
Around it
Before: company-knowledge.read-style-guide, spreadsheets.read-sheet. After: translation.translate-text, translation.translate-document.
Where this comes from
Weight 14 of 100 in Translation: 8 of 55 accounts; held slightly above its count because a silently changed term is the failure an agent cannot see
The same as data: /api/v1/use-cases/translation.keep-terms.json, or the MCP tool get_use_case with id translation.keep-terms. 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.