Head to head · Translate text · October 2026 research run

Lokalise vs Phrase

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

Which one, for what

Lokalise BB

Good 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 55
  • 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

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

Ahead on

  • Schema & documentation, 87 against 76

Watch for

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

Score by category

CategoryWeight this runLokalisePhraseEdge
Reliability16%208455Lokalise +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27687Phrase +11
Agent ergonomics13%16.26970Phrase +1
Security & auth14%17.57358Lokalise +15
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88483Lokalise +1
Transparency & trust7%8.88174Lokalise +7
Negative events≤1500
Total71.3 · BB64.2 · B

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-052026-10-06
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

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. No idempotency keys or deprecation policy were found in the reviewed documentation.

Phrase

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

Before you call either

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 four in parallel, and read X-Rate-Limit-Reset and X-Rate-Limit-Reason on a 429
  4. Send at most six texts of 2,000 characters to /v2/textTranslations, with consumerId and targetLang. Term bases and translation memories work only with an AI translation agent profile
  5. Use the MCP URL for the account's region, https://mcp.eu.phrase.com or https://mcp.us.phrase.com, and ask the user for the view consent alone unless the task writes

Questions

Which is better for AI agents, Lokalise or Phrase?

Lokalise scores 71.3 (BB) on agent readiness against Phrase's 64.2 (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.