Head to head · Translate text · October 2026 research run
Lingo.dev vs Phrase
Phrase scores 64.2 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 3 of 7 scored categories. Lingo.dev leads on reliability and agent ergonomics. Both do translate text.
Which one, for what
Good for Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.
Ahead on
- Reliability, 71 against 55
- Agent ergonomics, 75 against 70
Watch for
No public OpenAPI file was found, llms.txt holds one title line and docs pages have no Markdown version
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
- Schema & documentation, 87 against 54
- Payments & pricing, 30 against 20
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 this run | Lingo.dev | Phrase | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 71 | 55 | Lingo.dev +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 54 | 87 | Phrase +33 |
| Agent ergonomics | 13%16.2 | 75 | 70 | Lingo.dev +5 |
| Security & auth | 14%17.5 | 62 | 58 | Lingo.dev +4 |
| Payments & pricing | 10%12.5 | 20 | 30 | Phrase +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 87 | 83 | Lingo.dev +4 |
| Transparency & trust | 7%8.8 | 71 | 74 | Phrase +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 62.3 · B | 64.2 · B |
Facts side by side
| Fact | Lingo.dev | Phrase |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Replexica, Inc. | Phrase a.s. |
| Hosted endpoint | https://mcp.lingo.dev/account | https://mcp.eu.phrase.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The @lingo.dev/cli package states no licence on npm | 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 | dev.lingo/main | io.github.phrase/mcp |
| Last release | 2026-10-07 | 2026-10-06 |
| Terms last updated | 2026-05-07 | no date given |
| Privacy policy last updated | 2026-05-07 | 2026-10-06 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 5.4k stars, 92k npm/wk, 2k PyPI/wk | 49 stars, 40k npm/wk, 14k PyPI/wk |
Verdicts
Lingo.dev
Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its llms.txt is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.
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
Lingo.dev
- Send
X-API-Keyto https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can - Use
POST /process/localizefor one language pair andPOST /jobs/localizationwith anidempotencyKeyfor several. Pipeline stages run on async jobs only - Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff
- Read
usage.coston each sync response to track spend. Sandbox stops at 100,000 tokens a day - Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls
Phrase
- Exchange a Phrase Platform API token at
https://eu.phrase.com/idm/oauth/token(orus.phrase.com) for a Bearer JWT, which lasts about four hours, and refresh it before it expires - Send a
User-Agentheader naming your application on every Strings and TMS call. The Strings API answers 400 without one - Keep Strings calls under 1,000 in five minutes and four in parallel, and read
X-Rate-Limit-ResetandX-Rate-Limit-Reasonon a 429 - Send at most six texts of 2,000 characters to
/v2/textTranslations, withconsumerIdandtargetLang. Term bases and translation memories work only with an AI translation agent profile - Use the MCP URL for the account's region,
https://mcp.eu.phrase.comorhttps://mcp.us.phrase.com, and ask the user for the view consent alone unless the task writes
Questions
Which is better for AI agents, Lingo.dev or Phrase?
Phrase scores 64.2 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 3 of 7 scored categories. Lingo.dev leads on reliability and agent ergonomics.
Do Lingo.dev and Phrase need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Lingo.dev and Phrase without installing anything?
Yes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Phrase at https://mcp.eu.phrase.com.
Other comparisons with Lingo.dev or Phrase
- Amazon Translate vs Lingo.dev
- Amazon Translate vs Phrase
- Azure Translator vs Lingo.dev
- Azure Translator vs Phrase
- Crowdin vs Lingo.dev
- Crowdin vs Phrase
- DeepL API vs Lingo.dev
- DeepL API vs Phrase
- Google Cloud Translation vs Lingo.dev
- Google Cloud Translation vs Phrase
- Lara Translate API vs Lingo.dev
- Lara Translate API vs Phrase
- LibreTranslate vs Lingo.dev
- LibreTranslate vs Phrase
- Lingo.dev vs Lingvanex Translation API
- Lingo.dev vs Lokalise
- Lingo.dev vs SYSTRAN Translate API
- Lingvanex Translation API vs Phrase
- Lokalise vs Phrase
- Phrase vs SYSTRAN Translate API
Machine-readable
- This page as Markdown
/compare/lingo-dev-vs-phrase.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lingo-dev.json·/api/v1/tools/phrase.json - From a terminal
anchor compare lingo-dev phrase(the CLI) - Over MCP
compare_tools {"a": "lingo-dev", "b": "phrase"}at/mcp, no key