{ "data": { "a": { "slug": "lingvanex", "name": "Lingvanex Translation API", "vendor": "Lingvanex", "vendorUrl": "https://lingvanex.com/products/translationapi/", "kind": "http-api", "category": "translation", "summary": "Cloud machine translation API for text and HTML in about 110 languages, with auto-detection and transliteration, from a vendor that also sells on-premise translation servers.", "url": "https://www.anchorterminal.com/tools/lingvanex", "markdownUrl": "https://www.anchorterminal.com/tools/lingvanex.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lingvanex.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lingvanex.json", "transports": [ "http" ], "remoteUrl": "https://api-b2b.backenster.com/b1/api/v3", "packages": [ { "registry": "pypi", "name": "lingvanex" } ], "auth": "api-key", "authNotes": "`Authorization: Bearer \u003ckey\u003e` header. The key comes from the account panel after you add a payment method.", "pricing": "usage", "pricingNotes": "$5 per million characters. The API product page gives $3 per million for a pre-purchase of 1 billion characters or more and on-premise servers from $200 a month (https://lingvanex.com/products/translationapi/). The text API page gives $1 per million above 20 million, and on-premise at $10 a day as well as from $200 a month (https://lingvanex.com/services/translate-text-api/). A free trial is advertised with no amount stated, and a payment method comes before the API key.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 3, "asOf": "2026-09-30" }, "docsUrl": "https://docs.lingvanex.com/reference/overview", "openapi": "https://api.swaggerhub.com/apis/Lingvanex/lingvanex-b2b-api/1.0.0", "capabilities": [ "translate.text", "translate.detect" ], "tags": [ "hosted", "closed-source", "openapi", "python", "card-required" ], "graded": true, "anchor": { "graded": true, "score": 37, "grade": "F", "agentReady": false, "rank": 702, "ranked": true, "rankOf": 722, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 6, "payments": 15, "reliability": 40, "schema": 48, "security": 37, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "$5 per million characters list price. Product pages disagree on bulk and on-premise prices.", "bestFor": "Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.", "strengths": [ "$5 per million characters list price", "OpenAPI 3.0.3 document on SwaggerHub", "HTML mode, string arrays and transliteration in one call", "Better Stack status page for the Cloud API", "On-premise servers from the same vendor" ], "weaknesses": [ "Product pages disagree on bulk and on-premise prices", "The product page, privacy policy and API terms disagree on how long text is kept", "No published rate limits, and the terms let Lingvanex set them at its discretion", "No glossary or formality parameters, and only 200 and 403 documented", "No changelog, and the Python SDK hasn't changed since June 2024" ], "agentNotes": [ "Call the https:// server, not the http:// one the spec also lists", "Send `platform` as api on every call, since the spec marks it required", "Use locale codes such as en_GB and de_DE, not two-letter codes", "Check the `err` field on every response, since errors aren't only signalled by status code", "Send an array in `data` to translate several strings in one call" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 37 } ], "editorialScores": { "ergonomics": 50, "maintenance": 6, "payments": 15, "reliability": 40, "schema": 48, "security": 37, "transparency": 38 }, "provenanceScore": 57 }, "connect": { "http": "curl -X POST https://api-b2b.backenster.com/b1/api/v3/translate -H \"Authorization: Bearer $LINGVANEX_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"platform\":\"api\",\"from\":\"en_GB\",\"to\":\"de_DE\",\"data\":\"Your table is booked for seven.\"}'" }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lingvanex" }, "area": "everyday", "unitPrices": [ { "item": "Cloud API", "unit": "1m-chars", "usd": 5 }, { "item": "Cloud API, 1 billion pre-purchase", "unit": "1m-chars", "usd": 3, "note": "Another page quotes $1 per million above 20 million" } ], "provenance": { "legalEntity": "Nordicwise Limited", "domain": "lingvanex.com", "domainRegistered": "2016-12-28", "domainNote": "The API endpoint is on backenster.com (registered 2016-12-13). Its RDAP record doesn't name Lingvanex.", "endpointOnVendorDomain": false, "terms": "https://lingvanex.com/terms-of-use-of-api-lingvanex-translation/", "privacy": "https://lingvanex.com/privacy-policy/", "statusPage": "https://status.lingvanex.com", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-01", "notes": [ "The API terms give Nordicwise Limited, 52 1st April, 7600 Athienou, Larnaca, Cyprus.", "robots.txt blocked our fetch of lingvanex.com/.well-known/security.txt on the 30 September check.", "The developer docs on docs.lingvanex.com render only in a browser.", "status.lingvanex.com is a Better Stack page with one Cloud API component." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lingvanex.json", "live": { "slug": "lingvanex", "probe": { "target": "https://api-b2b.backenster.com/b1/api/v3", "method": "get", "lastAt": "2026-10-08T21:53:25.775122926Z", "lastOk": true, "lastStatus": 403, "lastMs": 245, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 143, "p95ms24h": 206, "samples24h": 270, "samples30d": 1962, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://status.lingvanex.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:45.24075776Z" }, "versions": [ { "registry": "pypi", "name": "lingvanex", "version": "0.0.11", "released": "2024-06-24", "seenAt": "2026-10-08T16:18:55.392831585Z" } ], "pypiWeekly": 7, "securityTxt": { "url": "https://lingvanex.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:07.52265725Z" }, "domain": { "domain": "lingvanex.com", "registered": "2016-12-28", "source": "https://rdap.verisign.com/com/v1/domain/lingvanex.com", "checkedAt": "2026-10-04T13:07:22.742489173Z" }, "pages": [ { "url": "https://lingvanex.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:21:35.53352143Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3f9363e612b5" }, { "url": "https://lingvanex.com/terms-of-use-of-api-lingvanex-translation/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:21:37.657662455Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "500498c858ff" } ], "updatedAt": "2026-10-08T21:53:25.775122926Z" } }, "answer": "Phrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "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:53:30.536669362Z", "lastOk": true, "lastStatus": 401, "lastMs": 57, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 60, "p95ms24h": 134, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://status.phrase.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:10.241168676Z" }, "updatedAt": "2026-10-08T21:58:10.241168676Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Lingvanex", "b": "Phrase a.s.", "name": "Vendor" }, { "a": "https://api-b2b.backenster.com/b1/api/v3", "b": "https://mcp.eu.phrase.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "not listed", "b": "io.github.phrase/mcp", "name": "MCP registry" }, { "a": "none", "b": "2026-10-06", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-01", "b": "2026-10-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "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": "3 PyPI/wk", "b": "49 stars, 40k npm/wk, 14k PyPI/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Phrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "question": "Which is better for AI agents, Lingvanex Translation API or Phrase?" }, { "answer": "Lingvanex Translation API needs an API key. Phrase takes an API key or an OAuth sign-in.", "question": "Do Lingvanex Translation API and Phrase need an API key?" }, { "answer": "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.", "question": "Can an agent call Lingvanex Translation API and Phrase without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.", "slug": "lingvanex", "watchFor": "Product pages disagree on bulk and on-premise prices" }, { "aheadOn": [ "Reliability, 55 against 40", "Schema \u0026 documentation, 87 against 48", "Agent ergonomics, 70 against 50", "Security \u0026 auth, 58 against 37", "Payments \u0026 pricing, 30 against 15", "Maintenance \u0026 community, 83 against 6", "Transparency \u0026 trust, 74 against 48" ], "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-lingvanex.json", "title": "Amazon Translate vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex" }, { "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-lingvanex.json", "title": "Azure Translator vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex" }, { "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-lingvanex.json", "title": "Crowdin vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lingvanex" }, { "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-lingvanex.json", "title": "DeepL API vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex" }, { "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-lingvanex.json", "title": "Google Cloud Translation vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex" }, { "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-lingvanex.json", "title": "Lara Translate API vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex" }, { "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-lingvanex.json", "title": "LibreTranslate vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex" }, { "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-phrase.json", "title": "Lingo.dev vs Phrase", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.json", "title": "Lingvanex Translation API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-systran.json", "title": "Lingvanex Translation API vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-systran" }, { "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": 15, "edge": "phrase", "key": "reliability", "lingvanex": 40, "name": "Reliability", "phrase": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 39, "edge": "phrase", "key": "schema", "lingvanex": 48, "name": "Schema \u0026 documentation", "phrase": 87, "weight": 13 }, { "by": 20, "edge": "phrase", "key": "ergonomics", "lingvanex": 50, "name": "Agent ergonomics", "phrase": 70, "weight": 13 }, { "by": 21, "edge": "phrase", "key": "security", "lingvanex": 37, "name": "Security \u0026 auth", "phrase": 58, "weight": 14 }, { "by": 15, "edge": "phrase", "key": "payments", "lingvanex": 15, "name": "Payments \u0026 pricing", "phrase": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 77, "edge": "phrase", "key": "maintenance", "lingvanex": 6, "name": "Maintenance \u0026 community", "phrase": 83, "weight": 7 }, { "by": 26, "edge": "phrase", "key": "transparency", "lingvanex": 48, "name": "Transparency \u0026 trust", "phrase": 74, "weight": 7 } ], "summary": "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.", "verdicts": { "lingvanex": "$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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase", "json": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase.md", "slim": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase.min.md" }, "markdown": "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.\n\n- 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\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### Lingvanex Translation API (F)\n\nGood for: Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.\n\nWatch for: Product pages disagree on bulk and on-premise prices\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- Reliability, 55 against 40\n- Schema \u0026 documentation, 87 against 48\n- Agent ergonomics, 70 against 50\n- Security \u0026 auth, 58 against 37\n- Payments \u0026 pricing, 30 against 15\n- Maintenance \u0026 community, 83 against 6\n- Transparency \u0026 trust, 74 against 48\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 | Lingvanex Translation API | Phrase | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 55 | Phrase +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 87 | Phrase +39 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 70 | Phrase +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 58 | Phrase +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 30 | Phrase +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 6 | 83 | Phrase +77 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 74 | Phrase +26 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **37 · F** | **64.2 · B** | |\n\n## Facts side by side\n\n| Fact | Lingvanex Translation API | Phrase |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lingvanex | Phrase a.s. |\n| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | `https://mcp.eu.phrase.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.github.phrase/mcp` |\n| Last release | none | 2026-10-06 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-05-01 | 2026-10-06 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 3 PyPI/wk | 49 stars, 40k npm/wk, 14k PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Lingvanex Translation API.** $5 per million characters list price. Product pages disagree on bulk and on-premise prices.\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### Lingvanex Translation API\n\n1. Call the https:// server, not the http:// one the spec also lists\n2. Send `platform` as api on every call, since the spec marks it required\n3. Use locale codes such as en_GB and de_DE, not two-letter codes\n4. Check the `err` field on every response, since errors aren't only signalled by status code\n5. Send an array in `data` to translate several strings in one call\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, Lingvanex Translation API or Phrase?\n\nPhrase scores 64.2 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.\n\n### Do Lingvanex Translation API and Phrase need an API key?\n\nLingvanex Translation API needs an API key. Phrase takes an API key or an OAuth sign-in.\n\n### Can an agent call Lingvanex Translation API and Phrase without installing anything?\n\nYes. Lingvanex Translation API has a hosted endpoint at https://api-b2b.backenster.com/b1/api/v3 and Phrase at https://mcp.eu.phrase.com.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingvanex\", \"b\": \"phrase\"}`. From a terminal: `anchor compare lingvanex phrase`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingvanex.json and https://www.anchorterminal.com/api/v1/tools/phrase.json\n\n## Other comparisons with Lingvanex Translation API or Phrase\n\n- [Amazon Translate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.md)\n- [Amazon Translate vs Phrase](https://www.anchorterminal.com/compare/amazon-translate-vs-phrase.md)\n- [Azure Translator vs Lingvanex Translation API](https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.md)\n- [Azure Translator vs Phrase](https://www.anchorterminal.com/compare/azure-translator-vs-phrase.md)\n- [Crowdin vs Lingvanex Translation API](https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.md)\n- [Crowdin vs Phrase](https://www.anchorterminal.com/compare/crowdin-vs-phrase.md)\n- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)\n- [DeepL API vs Phrase](https://www.anchorterminal.com/compare/deepl-api-vs-phrase.md)\n- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)\n- [Google Cloud Translation vs Phrase](https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.md)\n- [Lara Translate API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex.md)\n- [Lara Translate API vs Phrase](https://www.anchorterminal.com/compare/lara-translate-vs-phrase.md)\n- [LibreTranslate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex.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 Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)\n- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)\n- [Lingvanex Translation API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingvanex-vs-systran.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": "Lingvanex Translation API vs Phrase", "url": "" } ], "description": "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.", "facts": [ "Lingvanex Translation API F 37", "Phrase B 64.2", "scores" ], "h1": "Lingvanex Translation API vs Phrase", "image": "https://www.anchorterminal.com/assets/og/compare-lingvanex-vs-phrase.png", "path": "/compare/lingvanex-vs-phrase", "published": "2026-10-01", "section": "tools", "title": "Lingvanex Translation API vs Phrase for AI agents, F 37 vs B 64.2", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }