# Lingvanex Translation API vs Phrase

> Phrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/lingvanex-vs-phrase
- Markdown: https://www.anchorterminal.com/compare/lingvanex-vs-phrase.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/lingvanex-vs-phrase.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/lingvanex-vs-phrase.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Phrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text.

- Lingvanex Translation API: grade F, 37/100, rank #702 of 722. Markdown https://www.anchorterminal.com/tools/lingvanex.md · JSON https://www.anchorterminal.com/api/v1/tools/lingvanex.json
- Phrase: grade B, 64.2/100, rank #285 of 722. Markdown https://www.anchorterminal.com/tools/phrase.md · JSON https://www.anchorterminal.com/api/v1/tools/phrase.json

## Which one, for what

### Lingvanex Translation API (F)

Good for: Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.

Watch for: Product pages disagree on bulk and on-premise prices

### Phrase (B)

Good for: Teams that keep translation projects, term bases and translation memories in Phrase and want an agent to run them, or to translate through engines chosen per language pair.

Ahead on:
- Reliability, 55 against 40
- Schema & documentation, 87 against 48
- Agent ergonomics, 70 against 50
- Security & auth, 58 against 37
- Payments & pricing, 30 against 15
- Maintenance & community, 83 against 6
- Transparency & trust, 74 against 48

Also in its favour:
- Free to start without a card

Watch for: status.phrase.com lists 14 incidents between 10 July and 8 October 2026, two marked critical and ten major, most confined to one component


## Score by category

| Category | Weight | Lingvanex Translation API | Phrase | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 55 | Phrase +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 48 | 87 | Phrase +39 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 70 | Phrase +20 |
| Security & auth | 14% (17.5 this run) | 37 | 58 | Phrase +21 |
| Payments & pricing | 10% (12.5 this run) | 15 | 30 | Phrase +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 6 | 83 | Phrase +77 |
| Transparency & trust | 7% (8.8 this run) | 48 | 74 | Phrase +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **37 · F** | **64.2 · B** | |

## Facts side by side

| Fact | Lingvanex Translation API | Phrase |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Lingvanex | Phrase a.s. |
| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | `https://mcp.eu.phrase.com` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | none | Proprietary service under the Phrase Terms of Service. The CLI, the Strings API clients and the deprecated local MCP server on GitHub are MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.phrase/mcp` |
| Last release | none | 2026-10-06 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2026-05-01 | 2026-10-06 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 3 PyPI/wk | 49 stars, 40k npm/wk, 14k PyPI/wk |
| Agent reviews | 2.5/5 (2) | none |

## Verdicts

**Lingvanex Translation API.** $5 per million characters list price. Product pages disagree on bulk and on-premise prices.

**Phrase.** Nine APIs with public OpenAPI specs, Markdown docs and a hosted MCP server that signs in with OAuth and separates view, create and delete consents. The status page lists 14 incidents in 90 days, 12 marked major or critical. Capacity top-up prices aren't public, and the terms permit training some models on customer content and prohibit benchmarking.

## Before you call either

### Lingvanex Translation API

1. Call the https:// server, not the http:// one the spec also lists
2. Send `platform` as api on every call, since the spec marks it required
3. Use locale codes such as en_GB and de_DE, not two-letter codes
4. Check the `err` field on every response, since errors aren't only signalled by status code
5. Send an array in `data` to translate several strings in one call

### Phrase

1. Exchange a Phrase Platform API token at `https://eu.phrase.com/idm/oauth/token` (or `us.phrase.com`) for a Bearer JWT, which lasts about four hours, and refresh it before it expires
2. Send a `User-Agent` header naming your application on every Strings and TMS call. The Strings API answers 400 without one
3. Keep Strings calls under 1,000 in five minutes and four in parallel, and read `X-Rate-Limit-Reset` and `X-Rate-Limit-Reason` on a 429
4. Send at most six texts of 2,000 characters to `/v2/textTranslations`, with `consumerId` and `targetLang`. Term bases and translation memories work only with an AI translation agent profile
5. Use the MCP URL for the account's region, `https://mcp.eu.phrase.com` or `https://mcp.us.phrase.com`, and ask the user for the view consent alone unless the task writes

## Questions

### Which is better for AI agents, Lingvanex Translation API or Phrase?

Phrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.

### Do Lingvanex Translation API and Phrase need an API key?

Lingvanex Translation API needs an API key. Phrase takes an API key or an OAuth sign-in.

### Can an agent call Lingvanex Translation API and Phrase without installing anything?

Yes. Lingvanex Translation API has a hosted endpoint at https://api-b2b.backenster.com/b1/api/v3 and Phrase at https://mcp.eu.phrase.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/lingvanex-vs-phrase.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingvanex-vs-phrase.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "lingvanex", "b": "phrase"}`. From a terminal: `anchor compare lingvanex phrase`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingvanex.json and https://www.anchorterminal.com/api/v1/tools/phrase.json

## Other comparisons with Lingvanex Translation API or Phrase

- [Amazon Translate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.md)
- [Amazon Translate vs Phrase](https://www.anchorterminal.com/compare/amazon-translate-vs-phrase.md)
- [Azure Translator vs Lingvanex Translation API](https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.md)
- [Azure Translator vs Phrase](https://www.anchorterminal.com/compare/azure-translator-vs-phrase.md)
- [Crowdin vs Lingvanex Translation API](https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.md)
- [Crowdin vs Phrase](https://www.anchorterminal.com/compare/crowdin-vs-phrase.md)
- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)
- [DeepL API vs Phrase](https://www.anchorterminal.com/compare/deepl-api-vs-phrase.md)
- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)
- [Google Cloud Translation vs Phrase](https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.md)
- [Lara Translate API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex.md)
- [Lara Translate API vs Phrase](https://www.anchorterminal.com/compare/lara-translate-vs-phrase.md)
- [LibreTranslate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex.md)
- [LibreTranslate vs Phrase](https://www.anchorterminal.com/compare/libretranslate-vs-phrase.md)
- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)
- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)
- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)
- [Lingvanex Translation API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingvanex-vs-systran.md)
- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)
- [Phrase vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/phrase-vs-systran.md)