{ "data": { "a": { "slug": "lingo-dev", "name": "Lingo.dev", "vendor": "Replexica, Inc.", "vendorUrl": "https://lingo.dev", "kind": "http-api", "category": "translation", "summary": "Lingo.dev is a hosted AI translation platform from Replexica, Inc. Customers configure engines with glossaries, brand voices, rules and a model per language pair, then call them through a REST API, a CLI or a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/lingo-dev", "markdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lingo-dev.json", "repo": "https://github.com/lingodotdev/lingo.dev", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.lingo.dev/account", "packages": [ { "registry": "npm", "name": "@lingo.dev/cli" }, { "registry": "npm", "name": "lingo.dev" }, { "registry": "npm", "name": "@lingo.dev/_sdk" }, { "registry": "pypi", "name": "lingodotdev" } ], "auth": "mixed", "authNotes": "The REST API takes an API key in the `X-API-Key` header. A person creates the key in the dashboard after a browser signup, with no review or sales step. Personal keys exist on every plan and carry their creator's access. Organisation keys with their own role and engine scope need the Enterprise plan. The MCP server signs in through a browser with OAuth (authorisation code, PKCE, dynamic client registration) and the user picks one organisation on the consent screen. No OAuth scopes are published.", "pricing": "usage", "pricingNotes": "Usage is billed from prepaid credits with auto-reload. Lingo.dev charges $2 per million output tokens on top of the LLM provider's price, which is passed through with no markup, plus $0.50 per engine a month and $0.01 per AI review run. Sandbox has a $0 base and 100,000 tokens a day, so an agent's owner can start without a contract. Production is $99 a month with 5 million tokens a day, and Enterprise is custom. No free usage allowance was found, and whether signup needs a card could not be read without an account (https://lingo.dev/en/pricing, checked 2026-10-08).", "priceSummary": "$99 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or the pricing page. The API's 402 status means the organisation's credit limit was reached and carries no payment instructions (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 5402, "npmWeekly": 91991, "pypiWeekly": 1975, "asOf": "2026-10-08" }, "docsUrl": "https://lingo.dev/en/docs/api", "registryName": "dev.lingo/main", "capabilities": [ "translate.text", "translate.glossary", "translate.detect", "translate.formality" ], "tags": [ "hosted", "usage-priced", "prepaid", "mcp", "oauth", "api-key", "cli", "webhooks", "async-jobs", "typescript", "python", "closed-source", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 62.3, "grade": "B", "agentReady": false, "rank": 341, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 71, "schema": 54, "security": 62, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Glossary terms, per-locale brand voice and rules apply on every call, sync or async, through one configured engine", "Each sync response reports the model used, token counts and cost in USD", "Async jobs take up to 100 target locales, an `idempotencyKey`, signed webhooks and cursor paging with `limit` up to 100", "The hosted MCP server signs in with OAuth, PKCE and dynamic client registration, with no key to paste", "Public prices, a weekly changelog since March 2026 and an OpenStatus page with incident history" ], "weaknesses": [ "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version", "Organisation keys with their own role and engine scope, RBAC and audit logs are Enterprise only. On other plans every member is an Owner", "The status page lists two partial API outages in 90 days, on 18 July 2026 (closed after 19 hours) and 22 September 2026 (1 hour 50 minutes)", "Errors carry a status code and a free-text `message`, with no machine-readable code and no `Retry-After` documented", "The privacy policy points to lingo.dev/security for sub-processors, and that page returned 404 on 8 October 2026" ], "agentNotes": [ "Send `X-API-Key` to 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/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for 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.cost` on 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.3 } ], "editorialScores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 71, "schema": 54, "security": 62, "transparency": 51 }, "provenanceScore": 91 }, "connect": { "install": "npm install -g @lingo.dev/cli", "http": "curl -X POST https://api.lingo.dev/process/localize \\\n -H \"X-API-Key: your_api_key\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"engineId\": \"eng_abc123\", \"sourceLocale\": \"en\", \"targetLocale\": \"de\", \"data\": {\"greeting\": \"Hello\"}}'", "claudeCode": "claude mcp add lingo --transport http https://mcp.lingo.dev/account --scope user", "config": { "lingo": { "type": "http", "url": "https://mcp.lingo.dev/account" } } }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lingo-dev" }, "area": "everyday", "unitPrices": [ { "item": "Lingo.dev infrastructure fee", "unit": "1m-tokens", "usd": 2, "note": "Computed from output tokens. The LLM provider's price is added with no markup" }, { "item": "Production plan base", "unit": "month", "usd": 99, "note": "5 million tokens a day. Sandbox base is $0 with 100,000 a day" }, { "item": "Each engine", "unit": "month", "usd": 0.5, "note": "Per engine on Sandbox and Production" }, { "item": "AI review run", "unit": "call", "usd": 0.01, "note": "Per run" } ], "provenance": { "legalEntity": "Replexica, Inc.", "domain": "lingo.dev", "domainRegistered": "2021-05-03", "endpointOnVendorDomain": true, "terms": "https://lingo.dev/en/legal/terms", "privacy": "https://lingo.dev/en/legal/privacy", "statusPage": "https://status.lingo.dev", "changelog": "https://lingo.dev/en/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (last updated 7 May 2026) cover the website, the platform, the APIs, the CLI and the MCP server, name Replexica Inc. and Lingo.dev (Replexica, Inc), and are governed by Delaware law.", "The privacy policy (last updated 7 May 2026) covers the website and the platform, including content submitted for translation.", "The API answers at api.lingo.dev and the MCP server at mcp.lingo.dev, both on the vendor's domain.", "lingo.dev/.well-known/security.txt gives security@lingo.dev, a canonical URL and a disclosure policy with a safe-harbour promise. It has no Expires field.", "RDAP for lingo.dev gives a registration date of 2021-05-03. The site footer says the company is headquartered in San Francisco. No street address was found in the terms or the privacy policy.", "The privacy policy says the sub-processor list is kept in the Data Processing Agreement and at lingo.dev/security. That URL returned 404 on 8 October 2026 and no published DPA was found." ], "score": 91 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lingo-dev.json", "live": { "slug": "lingo-dev", "probe": { "target": "https://mcp.lingo.dev/account", "method": "get", "lastAt": "2026-10-08T21:12:14.053179587Z", "lastOk": true, "lastStatus": 401, "lastMs": 707, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 958, "p95ms24h": 1336, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.lingo.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:45.164350131Z" }, "updatedAt": "2026-10-08T21:12:14.053179587Z" } }, "answer": "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.", "b": { "slug": "phrase", "name": "Phrase", "vendor": "Phrase a.s.", "vendorUrl": "https://phrase.com", "kind": "http-api", "category": "translation", "summary": "Localisation platform from Phrase a.s. in Prague. Its Language AI API translates text and files through automatically selected machine translation engines, and its Strings and TMS APIs, CLI and hosted MCP server manage translation projects, term bases and translation memories.", "url": "https://www.anchorterminal.com/tools/phrase", "markdownUrl": "https://www.anchorterminal.com/tools/phrase.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/phrase.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/phrase.json", "repo": "https://github.com/phrase/phrase-cli", "license": "Proprietary service under the Phrase Terms of Service. The CLI, the Strings API clients and the deprecated local MCP server on GitHub are MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.eu.phrase.com", "packages": [ { "registry": "npm", "name": "phrase-js" }, { "registry": "pypi", "name": "phrase-api" }, { "registry": "npm", "name": "@phrase/phrase-mcp-server" } ], "auth": "mixed", "authNotes": "Self-serve. A user creates a Phrase Platform API token in profile settings and exchanges it at `/idm/oauth/token` for a Bearer JWT that lasts about four hours. Service accounts, added on 7 August 2026, use the OAuth client credentials grant and can be limited by product and scope. The hosted MCP server signs in with OAuth (PKCE, dynamic client registration or a client ID metadata document) and the user grants view, create, or modify and delete access. The Strings API also accepts its own access tokens with four scopes, Basic authentication with email and password, and an `access_token` query parameter.", "pricing": "paid", "pricingNotes": "Plans from $27 a month (Freelancer), $525 (Software UI/UX) and $1,245 (Team), billed annually, with Business and Enterprise quoted by sales. Each plan includes yearly capacities such as Machine Translation Units and TMS words, and top-up prices aren't public. A 14-day trial starts with an email address and a password, with no automatic charge afterwards, so an agent's owner can begin without a contract (checked 2026-10-08).", "priceSummary": "$27 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI specs or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 49, "npmWeekly": 40342, "pypiWeekly": 14166, "asOf": "2026-10-08" }, "docsUrl": "https://developers.phrase.com", "llmsTxt": "https://developers.phrase.com/llms.txt", "openapi": "https://developers.phrase.com/openapi/phrase-language-ai.json", "registryName": "io.github.phrase/mcp", "capabilities": [ "translate.text", "translate.documents", "translate.glossary", "translate.detect" ], "tags": [ "hosted", "paid", "trial", "no-card", "mcp", "oauth", "openapi", "llms-txt", "cli", "typescript", "python", "go", "eu", "status-page", "closed-source" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 64.2, "grade": "B", "agentReady": false, "rank": 285, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 83, "payments": 30, "reliability": 55, "schema": 87, "security": 58, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI specs for all nine APIs, an llms.txt index and a Markdown copy of every docs page, with a dated changelog of 51 entries since 24 April 2026", "Hosted MCP server in the EU and the US with OAuth, PKCE, dynamic client registration and three scopes, `phrase-mcp:read`, `phrase-mcp:write` and `phrase-mcp:destructive`", "Service accounts since 7 August 2026 use the OAuth client credentials grant, limited by product and scope, and don't count as seats", "Language AI picks the engine for each language pair, detects the source language and translates files with a quality estimate", "A 14-day trial starts with an email address and a password, and plan prices from $27 a month are public" ], "weaknesses": [ "status.phrase.com lists 14 incidents between 10 July and 8 October 2026, two marked critical and ten major, most confined to one component", "The terms of 4 October 2026 let Phrase train non-text models on customer content without approval, and prohibit use for benchmarking", "The Strings API still documents email and password Basic authentication and an `access_token` query parameter", "No idempotency keys, no `Retry-After` header in the docs and no published rate limit for the Language AI API", "The hosted MCP server's tool list isn't published, and the local npm server was deprecated on 7 August 2026, under six months after its first release" ], "agentNotes": [ "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", "Send a `User-Agent` header 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-Reset` and `X-Rate-Limit-Reason` on a 429", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.2 } ], "editorialScores": { "ergonomics": 70, "maintenance": 83, "payments": 30, "reliability": 55, "schema": 87, "security": 58, "transparency": 65 }, "provenanceScore": 82 }, "connect": { "install": "brew install phrase-cli", "http": "curl -X POST https://eu.phrase.com/idm/oauth/token -H 'Content-Type: application/x-www-form-urlencoded' -d 'grant_type=urn:ietf:params:oauth:grant-type:token-exchange' -d 'subject_token=API-TOKEN'", "claudeCode": "claude mcp add --transport streamable-http phrase-mcp-prod-eu https://mcp.eu.phrase.com" }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/phrase" }, "area": "everyday", "unitPrices": [ { "item": "Freelancer plan", "unit": "month", "usd": 27, "note": "Billed annually. 1 TMS seat, no Strings seats" }, { "item": "Software UI/UX plan", "unit": "month", "usd": 525, "note": "Billed annually. 15 Strings seats, 1,000,000 MTUs a year" }, { "item": "Team plan", "unit": "month", "usd": 1245, "note": "Billed annually. 20 Strings seats, 12,000,000 MTUs a year" } ], "provenance": { "legalEntity": "Phrase a.s.", "domain": "phrase.com", "domainRegistered": "1999-01-08", "endpointOnVendorDomain": true, "terms": "https://phrase.com/legal/", "privacy": "https://phrase.com/privacy/", "statusPage": "https://status.phrase.com", "changelog": "https://developers.phrase.com/en/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms name Phrase a.s. (formerly Memsource a.s.), Václavské náměstí 2132/47, 110 00 Prague 1, Czech Republic, identification number 247 07 139. A second tab holds the terms of Phrase GmbH in Hamburg.", "phrase.com/legal/ carries the full Phrase a.s. Terms of Service with its Data Processing Addendum, effective 4 October 2026, plus the Fair Use Policy and the Platform Pricing Terms on further tabs. phrase.com/terms/ redirects to it.", "The privacy notice for users and clients was last updated on 6 October 2026 and names Phrase a.s. and Phrase GmbH as controllers.", "phrase.com/.well-known/security.txt and developers.phrase.com/.well-known/security.txt both return 404. The security page takes reports at security@phrase.com.", "The Strings, Language AI, Platform and MCP hosts are on phrase.com. The TMS OpenAPI spec names cloud.memsource.com, the product's earlier domain.", "RDAP for phrase.com gives a registration date of 1999-01-08." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/phrase.json", "live": { "slug": "phrase", "probe": { "target": "https://mcp.eu.phrase.com", "method": "get", "lastAt": "2026-10-08T21:12:18.37223698Z", "lastOk": true, "lastStatus": 401, "lastMs": 71, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 63, "p95ms24h": 134, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.phrase.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:21.711443908Z" }, "updatedAt": "2026-10-08T21:12:18.37223698Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Replexica, Inc.", "b": "Phrase a.s.", "name": "Vendor" }, { "a": "https://mcp.lingo.dev/account", "b": "https://mcp.eu.phrase.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary service under the Phrase Terms of Service. The CLI, the Strings API clients and the deprecated local MCP server on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "dev.lingo/main", "b": "io.github.phrase/mcp", "name": "MCP registry" }, { "a": "2026-10-07", "b": "2026-10-06", "name": "Last release" }, { "a": "2026-05-07", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-07", "b": "2026-10-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "5.4k stars, 92k npm/wk, 2k PyPI/wk", "b": "49 stars, 40k npm/wk, 14k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Lingo.dev or Phrase?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Lingo.dev and Phrase need an API key?" }, { "answer": "Yes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Phrase at https://mcp.eu.phrase.com.", "question": "Can an agent call Lingo.dev and Phrase without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 71 against 55", "Agent ergonomics, 75 against 70" ], "also": null, "goodFor": "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.", "slug": "lingo-dev", "watchFor": "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version" }, { "aheadOn": [ "Schema \u0026 documentation, 87 against 54", "Payments \u0026 pricing, 30 against 20" ], "also": [ "Free to start without a card" ], "goodFor": "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.", "slug": "phrase", "watchFor": "status.phrase.com lists 14 incidents between 10 July and 8 October 2026, two marked critical and ten major, most confined to one component" } ], "job": { "capability": "translate.text", "name": "Translate text" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.json", "title": "Amazon Translate vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-phrase.json", "title": "Amazon Translate vs Phrase", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.json", "title": "Azure Translator vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/azure-translator-vs-phrase.json", "title": "Azure Translator vs Phrase", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.json", "title": "Crowdin vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/crowdin-vs-phrase.json", "title": "Crowdin vs Phrase", "url": "https://www.anchorterminal.com/compare/crowdin-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.json", "title": "DeepL API vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/deepl-api-vs-phrase.json", "title": "DeepL API vs Phrase", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.json", "title": "Google Cloud Translation vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.json", "title": "Google Cloud Translation vs Phrase", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.json", "title": "Lara Translate API vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/lara-translate-vs-phrase.json", "title": "Lara Translate API vs Phrase", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.json", "title": "LibreTranslate vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/libretranslate-vs-phrase.json", "title": "LibreTranslate vs Phrase", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.json", "title": "Lingo.dev vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json", "title": "Lingo.dev vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran.json", "title": "Lingo.dev vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase.json", "title": "Lingvanex Translation API vs Phrase", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-phrase.json", "title": "Lokalise vs Phrase", "url": "https://www.anchorterminal.com/compare/lokalise-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/phrase-vs-systran.json", "title": "Phrase vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/phrase-vs-systran" } ], "scores": [ { "by": 16, "edge": "lingo-dev", "key": "reliability", "lingo-dev": 71, "name": "Reliability", "phrase": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "phrase", "key": "schema", "lingo-dev": 54, "name": "Schema \u0026 documentation", "phrase": 87, "weight": 13 }, { "by": 5, "edge": "lingo-dev", "key": "ergonomics", "lingo-dev": 75, "name": "Agent ergonomics", "phrase": 70, "weight": 13 }, { "by": 4, "edge": "lingo-dev", "key": "security", "lingo-dev": 62, "name": "Security \u0026 auth", "phrase": 58, "weight": 14 }, { "by": 10, "edge": "phrase", "key": "payments", "lingo-dev": 20, "name": "Payments \u0026 pricing", "phrase": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "lingo-dev", "key": "maintenance", "lingo-dev": 87, "name": "Maintenance \u0026 community", "phrase": 83, "weight": 7 }, { "by": 3, "edge": "phrase", "key": "transparency", "lingo-dev": 71, "name": "Transparency \u0026 trust", "phrase": 74, "weight": 7 } ], "summary": "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase", "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md", "slim": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.min.md" }, "markdown": "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.\n\n- Lingo.dev: grade B, 62.3/100, rank #341 of 722. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json\n- 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\n\n## Which one, for what\n\n### Lingo.dev (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 71 against 55\n- Agent ergonomics, 75 against 70\n\nWatch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version\n\n### Phrase (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 87 against 54\n- Payments \u0026 pricing, 30 against 20\n\nAlso in its favour:\n- Free to start without a card\n\nWatch 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\n\n\n## Score by category\n\n| Category | Weight | Lingo.dev | Phrase | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 55 | Lingo.dev +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 87 | Phrase +33 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 70 | Lingo.dev +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 58 | Lingo.dev +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | Phrase +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 83 | Lingo.dev +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 74 | Phrase +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.3 · B** | **64.2 · B** | |\n\n## Facts side by side\n\n| Fact | Lingo.dev | Phrase |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Replexica, Inc. | Phrase a.s. |\n| Hosted endpoint | `https://mcp.lingo.dev/account` | `https://mcp.eu.phrase.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `dev.lingo/main` | `io.github.phrase/mcp` |\n| Last release | 2026-10-07 | 2026-10-06 |\n| Terms last updated | 2026-05-07 | no date given |\n| Privacy policy last updated | 2026-05-07 | 2026-10-06 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 5.4k stars, 92k npm/wk, 2k PyPI/wk | 49 stars, 40k npm/wk, 14k PyPI/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Lingo.dev\n\n1. Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can\n2. Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only\n3. Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff\n4. Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day\n5. 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\n\n### Phrase\n\n1. 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\n2. Send a `User-Agent` header naming your application on every Strings and TMS call. The Strings API answers 400 without one\n3. 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\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Lingo.dev or Phrase?\n\nPhrase 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.\n\n### Do Lingo.dev and Phrase need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Lingo.dev and Phrase without installing anything?\n\nYes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Phrase at https://mcp.eu.phrase.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingo-dev\", \"b\": \"phrase\"}`. From a terminal: `anchor compare lingo-dev phrase`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingo-dev.json and https://www.anchorterminal.com/api/v1/tools/phrase.json\n\n## Other comparisons with Lingo.dev or Phrase\n\n- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)\n- [Amazon Translate vs Phrase](https://www.anchorterminal.com/compare/amazon-translate-vs-phrase.md)\n- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)\n- [Azure Translator vs Phrase](https://www.anchorterminal.com/compare/azure-translator-vs-phrase.md)\n- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)\n- [Crowdin vs Phrase](https://www.anchorterminal.com/compare/crowdin-vs-phrase.md)\n- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)\n- [DeepL API vs Phrase](https://www.anchorterminal.com/compare/deepl-api-vs-phrase.md)\n- [Google Cloud Translation vs Lingo.dev](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md)\n- [Google Cloud Translation vs Phrase](https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.md)\n- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)\n- [Lara Translate API vs Phrase](https://www.anchorterminal.com/compare/lara-translate-vs-phrase.md)\n- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)\n- [LibreTranslate vs Phrase](https://www.anchorterminal.com/compare/libretranslate-vs-phrase.md)\n- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)\n- [Lingvanex Translation API vs Phrase](https://www.anchorterminal.com/compare/lingvanex-vs-phrase.md)\n- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)\n- [Phrase vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/phrase-vs-systran.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lingo.dev vs Phrase", "url": "" } ], "description": "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. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Lingo.dev B 62.3", "Phrase B 64.2", "scores" ], "h1": "Lingo.dev vs Phrase", "image": "https://www.anchorterminal.com/assets/og/compare-lingo-dev-vs-phrase.png", "path": "/compare/lingo-dev-vs-phrase", "published": "2026-10-01", "section": "tools", "title": "Lingo.dev vs Phrase for AI agents, B 62.3 vs B 64.2 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase" }, "tokens": { "markdown": 2450, "slim": 730 }, "version": 1 }