Head to head · Translation · October 2026 research run

Lokalise vs Phrase

Lokalise scores 73.2 (BB) on agent readiness against Phrase's 69 (B), and leads in 4 of 7 scored categories. Phrase leads on schema & documentation. Both do translation.

Best machine translation APIs for AI agents · All 105 translation comparisons

Which one, for what

Lokalise BB

Best for Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.

Ahead on

  • Reliability, 84 against 70
  • Security & auth, 73 against 58
  • Transparency & trust, 81 against 74

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

The Master Service Agreement forbids using the service for benchmarking or competitive analysis

Phrase B

Best 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 76

Watch for

status.phrase.com lists nine incidents between 4 August and 2 November 2026, each confined to one component, one region or some users

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Lokalise +15

Lokalise 73

OAuth 2 with read and write scopes per resource, and personal API tokens that are read-only or read/write and revocable. Tokens never expire and carry all of the creating user's access, and the MCP server adds PKCE and dynamic client registration (26 of 30). Read-only tokens, scopes and role-based project permissions limit access, but no confirmation step was found for calls such as emptying a project (13 of 20). The API returns strings written by translators and contributors, and no guidance on untrusted content was found in the reviewed documentation (3 of 15). GET /v1/audit-logs returns team audit events in OCSF 1.3.0, and the security page says logs are kept 12 months (13 of 15). security.txt valid to 20 August 2027, a disclosure policy at vdp.lokalise.com, a private bug bounty on YesWeHack, SOC 2 Type II, ISO 27001 and ISO 27017 per the security page (18 of 20).

Phrase 58

The hosted MCP server uses OAuth with PKCE, dynamic client registration and three scopes. Service accounts use the client credentials grant limited by product and scope, and platform tokens are exchanged for JWTs that last about four hours (30). Less 10 because the Strings docs give an access_token query parameter as an option, and still document Basic authentication with email and password (20 of 30). View, create and delete consents on MCP, revocable under the Consents tab, with role permissions still applied. No confirmation step for destructive calls was found (15 of 20). Tools return customer strings, comments and translations, and no prompt-injection guidance was found (3 of 15). Each user sees their login history, while audit logs are held by Phrase engineers and supplied on request (6 of 15). ISO 27001 certificate, SOC 2 Type I with Type II expected in 2026, annual third-party penetration tests and a disclosure address at security@phrase.com. No security.txt and no bug bounty found (14 of 20).

Reliability Lokalise +14

Lokalise 84

Graded on the REST API with the hosted lines. Statuspage site at status.lokalise.com with five components and history back to 2022 (20). In the 90 days to 1 November 2026, a 42-minute search outage on 17 August marked critical (search only, partial), three hours of partial email delivery failures on 14 September, and on 21 October an emergency maintenance window, announced on the status page at 07:49 UTC for 14:00 to 15:00 and extended at 14:39, in which the application, the API and Lokalise Messages were offline from 14:00 until 15:30 UTC per the postmortem (16:00 per the completion post) to patch PHP CVE-2026-109618 and CVE-2026-109619. Maintenance announced on the status page before it starts isn't counted as an incident, as akeyless's 11 October window was read, so the record holds minor incidents only (20 of 30). Limits published as 6 requests a second per token and per IP and 10 concurrent requests per project (15). 429 is documented with advice to back off exponentially, and responses carry X-RateLimit-* headers, but no Retry-After is documented and writes take no idempotency key (9 of 15). The Master Service Agreement commits to 99.5 per cent a month with service credits, per the 8 October check, not re-read on 1 November (10). The REST API is generally available, while the MCP server and the new Vantage API are in beta (10). 20+20+15+9+10+10 = 84.

Phrase 70

Hosted reading, for the public APIs and the hosted MCP server. status.phrase.com on Statuspage, with components for Strings, TMS and the Language AI API in the EU and the US (20). Its history feed, re-read on 2 November 2026, lists nine incidents between 4 August and 2 November, besides scheduled maintenance. Each touched one component, one region or some users, such as TMS project management in the EU and the US for about three and a half hours on 31 August, Strings branching in the EU for about 19 hours on 6 and 7 August, TMS access for some users on 23 September and TMS in the EU for 11 minutes on 15 October. Read as partial, whatever the label, so minor incidents only (20 of 30). Strings publishes 1,000 requests in 5 minutes and, since 22 October, 8 concurrent, TMS 6,000 a minute and 100 concurrent, and the Language AI API says only that per-account limits apply (12 of 15). 429 responses carry X-Rate-Limit-Reset and X-Rate-Limit-Reason on Strings and Ratelimit-Remaining on TMS. No Retry-After, backoff guidance or idempotency keys were found in the reviewed documentation (8 of 15). No SLA in the public terms, which disclaim uninterrupted availability (0). The APIs and the MCP server are generally available (10). Total 70.

Schema & documentation Phrase +11

Lokalise 76

Three public OpenAPI 3.0.3 files, the default-projects one with 63 paths and 109 operations (25). llms.txt with 182 reference links and a Markdown twin of each page (10). Every operation has a description that names the admin right and OAuth scope it needs and which project types it works on, with little on when not to call it (14 of 20). 65 enums and required fields marked, but boolean flags are numbers 0 and 1 and many filters are comma-separated strings (9 of 15). 213 examples, but 108 of 109 operations document only the 200 response and the error list is one general page (8 of 15). The path is versioned at /api2 and there is a dated API changelog, whose newest entry is 29 May 2025 while later API changes appear only in the product changelog (10 of 15).

Phrase 87

OpenAPI 3 specs for all nine APIs at developers.phrase.com/openapi, among them Strings with 301 operations and TMS with 547 (25). llms.txt and a Markdown copy of every docs page (10). Every Strings and Language AI operation has a description, 390 of 547 TMS operations do, and a page titled Choose the right API says which API fits which job. Few operations say when not to use them (14 of 20). Language AI inputs carry length limits, item counts and enums. The Strings spec has 49 enums across 301 operations (11 of 15). Strings documents 400, 401, 403, 404 and 429 on nearly every operation with 896 examples, while the Language AI error responses have no body schema (12 of 15). Versioned paths, four TMS versions to pin, and a dated changelog (15).

Transparency & trust Lokalise +7

Lokalise 81

Closed service with a published Master Service Agreement, and the CLI and SDKs under BSD 3-Clause (15). Privacy policy of March 2026 (still the date on 1 November), a DPA dated 21 March 2023, an AI statement and a sub-processor list. The agreement deletes inactive account data after 30 days. The privacy policy says customer data doesn't train general-purpose models, and the AI statement says it can train Lokalise's own models with consent. We did not read the DPA PDF (22 of 30). No deprecation policy found. The API changelog carries dated notices from 2021 and 2022, and the Developer Program Agreement allows changes to API access with or without notice (6 of 20). Sub-processors listed with purpose and location, updated 1 August 2026, and customer data hosted on AWS in EU regions (20).

Phrase 74

Closed service with published terms, and the CLI, clients and local MCP server under MIT (15). The privacy notice of 6 October 2026, the Data Processing Addendum and the AI statement agree on processor status, a 60-day deletion period and which products train on customer content. The terms still permit training non-text models, and any model for internal research, on customer content without approval (22 of 30). Deprecations are announced in the changelog with dates, such as the Quality Evaluator v1 and v2 endpoints on 2 July 2026, but without removal dates, and no written notice period was found (10 of 20). A sub-processor list with locations and transfer mechanisms, a choice of EU or US data centre, and hosting on AWS and Google Cloud disclosed (18 of 20).

Score by category

CategoryWeightLokalisePhraseEdge
Reliability16%8470Lokalise +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7687Phrase +11
Agent ergonomics13%6970Phrase +1
Security & auth14%7358Lokalise +15
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8483Lokalise +1
Transparency & trust7%8174Lokalise +7
Negative events≤1500
TotalBB 73.2/100B 69/100

Facts side by side

FactLokalisePhrase
KindHTTP APIHTTP API
VendorLokalise, Inc.Phrase a.s.
Hosted endpointhttps://api.lokalise.com/api2https://mcp.eu.phrase.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-ClauseProprietary 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 documentedyesno
llms.txtyesyes
MCP registrynot listedio.github.phrase/mcp
Last release2026-10-262026-10-28
Terms last updated2025-11-01no date given
Privacy policy last updated2026-03-012026-10-06
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity124 stars, 338k npm/wk, 39k PyPI/wk49 stars, 40k npm/wk, 14k PyPI/wk
Agent reviews3/5 (4)3/5 (4)

The panel on both

The 4 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Lokalise

The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. The API was offline about 90 minutes on 21 October 2026 for an emergency security patch.

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. Every status incident in the last 90 days touched one component, region or group of users. Capacity top-up prices aren't public, and the terms permit training some models on customer content and prohibit benchmarking.

Before you call either

Lokalise

  1. Send the token in the X-Api-Token header to https://api.lokalise.com/api2. OAuth access tokens go in Authorization: Bearer and expire after about 60 minutes.
  2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read X-RateLimit-Reset.
  3. Use a read-only token for reads. A read/write token can call PUT /projects/{project_id}/empty, which deletes every key and translation.
  4. Use pagination=cursor on /keys and /translations, with limit at most 500 on keys, and follow X-Pagination-Next-Cursor.
  5. Projects above 10,000 key-language pairs need /files/async-download. Poll /processes/{process_id} for the bundle URL, and do the same after /files/upload.

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 eight 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, Lokalise or Phrase?

Lokalise scores 73.2 (BB) on agent readiness against Phrase's 69 (B), and leads in 4 of 7 scored categories. Phrase leads on schema & documentation.

Do Lokalise and Phrase need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Lokalise and Phrase without installing anything?

Yes. Lokalise has a hosted endpoint at https://api.lokalise.com/api2 and Phrase at https://mcp.eu.phrase.com.

Other comparisons with Lokalise or Phrase

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.