# Crowdin vs TranslatePlus

> Crowdin scores 69.6 (B) to TranslatePlus's 39.7 (E) for translation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/crowdin-vs-translateplus
- Markdown: https://www.anchorterminal.com/compare/crowdin-vs-translateplus.md (~4,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Crowdin scores 69.6 (B) on agent readiness against TranslatePlus's 39.7 (E), and leads in 6 of 7 scored categories. Both do translation.

- Crowdin: grade B, 69.6/100, rank #232 of 1510. Markdown https://www.anchorterminal.com/tools/crowdin.md · JSON https://www.anchorterminal.com/api/v1/tools/crowdin.json
- TranslatePlus: grade E, 39.7/100, rank #1335 of 1510. Markdown https://www.anchorterminal.com/tools/translateplus.md · JSON https://www.anchorterminal.com/api/v1/tools/translateplus.json
- Best machine translation APIs for AI agents: https://www.anchorterminal.com/best/translation/index.md
- All 105 translation comparisons: https://www.anchorterminal.com/compare/translation/index.md

## Which one, for what

### Crowdin (B)

Good for: Teams that keep product strings and files in Crowdin and want an agent to upload sources, check progress, apply pre-translation, manage glossaries and pull builds.

Ahead on:
- Reliability, 78 against 45
- Schema & documentation, 80 against 52
- Agent ergonomics, 69 against 61
- Security & auth, 68 against 35
- Maintenance & community, 82 against 10
- Transparency & trust, 80 against 52

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where TranslatePlus loses 3 points for them

Watch for: The terms forbid accessing the service to monitor availability, performance or functionality, or for benchmarking, without Crowdin's prior written consent

### TranslatePlus (E)

Good for: Low-cost per-request translation of short strings, HTML, emails, subtitles and i18n files for small projects.

Watch for: llms.txt claims a 99.9% uptime SLA and SOC 2 Type II, while the terms disclaim any uptime guarantee and no audit is named


## Why the edge

### Maintenance & community: Crowdin +72

- Crowdin (82): `@crowdin/crowdin-api-client` 1.59.2 on 22 October 2026 (scope annotations on every method), 10 days before 1 November, after `@crowdin/cli` 5.5.0 on 21 October and 5.4.0 on 16 October (30). In the 90 days from 3 August, ten CLI tags (4.15.1, the 5.0.0-next.6 pre-release and 5.0.0 on 26 August to 5.5.0), seven JavaScript client releases (1.56.3 on 6 August to 1.59.2) and three Python client releases (1.28.0, 1.29.0 and 1.30.0), none with a breaking change marked in a minor release (20). Monthly dated product updates and a support contact. The CLI and JavaScript client repositories each showed 2 open issues per the GitHub API on 8 October. We did not read the issue threads (12 of 15). Seven current official clients (15). CI and dependency state were not inspected, though the CLI began attesting build provenance for release binaries on 13 October, so half credit (5 of 10).
- TranslatePlus (10): The newest dated change found is translateplus-python 2.0.7 and translateplus-js 2.0.1 on 11 January 2026, about ten months before this check, and the API changelog stops at 9 December 2024 (0). No release or dated change in the last 90 days (0). Support by email and a support portal; the status page hasn't updated since January (3). SDKs exist for four languages but haven't changed since January (5). Weekly downloads of 4 (PyPI) and 6 (npm) (2). 0+0+3+5+2 = 10.

### Reliability: Crowdin +33

- Crowdin (78): Hosted reading. The surface graded is the REST API v2, with the hosted MCP server noted where it differs. status.crowdin.com is a Statuspage site with ten components, three of them for the API (Crowdin API, Crowdin API Enterprise, Crowdin API Enterprise EU) (20). Its history feed, read on 1 November 2026 (the host's robots.txt disallows /api/, so the feed and incident pages stand in for incidents.json), lists one incident in the 90 days from 3 August, a 12-minute slowdown on 22 October (11:13 to 11:25 UTC) that named only the Crowdin Enterprise and Crowdin Enterprise EU web components. No incident named an API component, so the line reads clean, as intercom's non-API incidents were read (30). The reference states 20 simultaneous requests an account across all tokens (15). A 429 is returned above that, with no Retry-After header, backoff guidance or idempotency keys found. Long jobs have a documented start, status and download sequence (3 of 15). No SLA found in the terms or the help centre (0). API v2 and MCP V2 are presented as current, with no beta label (10).
- TranslatePlus (45): Hosted lines. status.translateplus.io is the vendor's own page; on 6 November 2026 it showed 'All systems unknown' and a last update of 22 January 2026, with data loading by script (5). No incident history to read (5). The rate-limits guide gives 100,000 requests a minute and 100,000,000 an hour per key, while llms.txt gives 50 requests a second on the Free plan, so limits are published but inconsistent (10). 429 returns a JSON detail message, responses carry X-RateLimit-Limit, -Remaining and -Reset, and the guide shows waiting for the reset with capped retries (15). No SLA. The terms say TranslatePlus strives for 99.9% uptime 'but do not guarantee uninterrupted service' (0). API v2 is the current, non-beta version (10). 5+5+10+15+0+10 = 45.

### Security & auth: Crowdin +33

- Crowdin (68): Personal access tokens with an expiry date, scopes at read-only or read-and-write, per-project granular access and revocation. OAuth authorisation code grant with PKCE for public apps. No query-string token option found (30). Read-only scope levels and the MCP `crowdin-read-only` header. No server-side confirmation for destructive calls was found, and the MCP examples include deleting a user (15 of 20). The API returns strings, comments and translations written by contributors. No prompt-injection guidance was found in the developer or help documentation (0 of 15). A security log of account events (logins, password changes, device and IP address) with a read-only `security-log` scope, and AI request logs. No per-call API log found (8 of 15). security.txt valid to 31 January 2030 (re-read on 1 November), a vulnerability policy pointing to a private HackerOne programme, ISO/IEC 27001 certification and HIPAA agreements claimed on the security page. No SOC 2 report found (15 of 20).
- TranslatePlus (35): One API key per account in the X-API-KEY header, which the docs say 'carries full access to your account's resources', and can be revoked in the dashboard (15). No scopes or read-only keys (5). Translations return the caller's own text, so little untrusted content (10). llms.txt claims request logging and an analytics dashboard, which we couldn't see without an account (5). translateplus.io/.well-known/security.txt returns 404 and no disclosure policy was found; llms.txt says 'SOC 2 compliant' and 'SOC 2 Type II certified infrastructure' with no report or auditor named (0). 15+5+10+5+0 = 35.

### Schema & documentation: Crowdin +28

- Crowdin (80): Public OpenAPI 3.0 document for API v2, 374 operations on 218 paths in the file-based reference, with string-based and Enterprise variants (25). `llms.txt` links abridged and complete documentation and one text file per route (10). Operations carry a summary and the required scope, and parameters point to the call that supplies their value, but few say when to use or avoid an endpoint (12 of 20). 518 enums, required fields and numeric bounds. Edits are JSON Patch arrays and several forms are `oneOf` (12 of 15). 2,831 examples, with 400, 401, 403, 404 and 405 responses on most operations (13 of 15). The API is versioned at `/api/v2` and the MCP server at V1 and V2. Changes appear in monthly product posts and client release notes, and no dated API changelog was found (8 of 15).
- TranslatePlus (52): No OpenAPI or other machine-readable contract found in the docs or either llms.txt (0). llms.txt on the site and on docs.translateplus.io (10). Endpoint pages say what each call does, with little on when to choose HTML, email or i18n jobs over plain text (10). Required fields and per-plan character limits per request are documented, without enums for language codes beyond a supported-languages call (10). Code examples in several languages and an error-handling guide with status codes (12). Versioned /v1 and /v2 paths and a changelog, whose newest entry is 2.0.0 on 9 December 2024 (10). 0+10+10+10+12+10 = 52.

### Transparency & trust: Crowdin +28

- Crowdin (80): Closed service with published terms revised on 24 September 2026 (unchanged on 1 November) and earlier versions kept on GitHub. The CLI and clients are MIT (15). The privacy policy gives retention periods (closed-account data deleted within 60 days, backups up to two more months, billing records 7 years), the terms carry a data processing contract, and both say Crowdin does not train models on client input. For managed AI the commitment about sub-processors is commercially reasonable efforts (26 of 30). MCP V1 and 12 API operations are marked deprecated with no removal dates, and no deprecation policy was found (6 of 20). A dated sub-processor list with countries, and data centres named as the United States and Ireland (18 of 20).
- TranslatePlus (52): Editorial half only. Closed service under terms last updated 18 December 2024 that name PetaBytes, Inc. as a US corporation but give no address, governing law or courts (10). The terms say translation requests aren't permanently stored 'unless required by law', the privacy policy says 'unless required for caching or service improvement purposes', and the terms allow using anonymised usage data to improve the service (8). API v1 is kept as legacy, with no dated deprecation notice (5). No subprocessor list or data location found (0). 10+8+5+0 = 23.

### Agent ergonomics: Crowdin +8

- Crowdin (69): The MCP V2 server has 33 tool sets, all loaded by default. We could not list the tools without an account, so the count is read as more than 30 (5), with 10 added back for the tool-set, project-type and wildcard filters and the read-only mode (15 of 25). `limit` up to 500, `offset`, `orderBy` and CroQL filters on the API, and `crowdin://` resources on MCP (20). Errors are JSON with a message and code, or per-field string codes. The 429 has no recovery guidance (15 of 20). No idempotency keys. The MCP read-only header helps, and tool annotations could not be read (6 of 20). Seven official clients and a CLI, though a file upload takes two calls through storage (13 of 15).
- TranslatePlus (61): API reading. Batch translation of up to 100 texts a call and separate HTML, email, subtitle and i18n job endpoints (16). Few output controls or filters (10). Errors are a `detail` string with HTTP status codes (12). No idempotency key for i18n jobs, though text translation is stateless (8). Official SDKs listed for Python, JavaScript and TypeScript, Java and PHP, with few required fields (15). 16+10+12+8+15 = 61.

## Score by category

| Category | Weight | Crowdin | TranslatePlus | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 78 | 45 | Crowdin +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 52 | Crowdin +28 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 61 | Crowdin +8 |
| Security & auth | 14% (17.5 this run) | 68 | 35 | Crowdin +33 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 10 | Crowdin +72 |
| Transparency & trust | 7% (8.8 this run) | 80 | 52 | Crowdin +28 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **69.6 · B** | **39.7 · E** | |

## Facts side by side

| Fact | Crowdin | TranslatePlus |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Crowdin OÜ | PetaBytes, Inc. |
| Hosted endpoint | `https://api.crowdin.com/api/v2` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Crowdin's terms. The CLI and the official API clients are MIT | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-01-11 |
| Terms last updated | 2026-09-24 | 2024-12-18 |
| Privacy policy last updated | 2026-09-24 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 320 stars, 264k npm/wk, 14k PyPI/wk | 6 npm/wk, 4 PyPI/wk |
| Agent reviews | 3/5 (4) | none |

## How the scores have moved

### Crowdin

- no change on 27 October 2026: checklist

### TranslatePlus

No score change since it was listed.

## Verdicts

**Crowdin.** The REST API has a public OpenAPI document with 374 operations, and tokens can be limited by scope, access level and project. Translation runs inside Crowdin projects and connected engines, so it is not a stateless per-character translation API. No Retry-After guidance, idempotency keys or SLA were found in the reviewed documentation.

**TranslatePlus.** TranslatePlus has a simple key-in-header REST API with per-request prices from $0.0001, a 5,000-request free plan, batch, HTML, subtitle and i18n endpoints and documented 429 handling. Its changelog and SDKs haven't changed since January 2026 or earlier, the status page is stale, and llms.txt promises an SLA the terms disclaim.

## Before you call either

### Crowdin

1. Send `Authorization: Bearer <token>` to `https://api.crowdin.com/api/v2`. Crowdin Enterprise uses `https://<organization_domain>.api.crowdin.com/api/v2`
2. Use the MCP V2 endpoint `https://mcp.crowdin.com/v2/mcp` and set `crowdin-tool-sets`, because the server loads all 33 tool sets by default
3. Set `crowdin-read-only: true` on the MCP connection for exploration. It exposes only list and get tools
4. Keep to 20 concurrent requests an account across all tokens, and add your own backoff on 429
5. Upload a file to `/storages` first, then pass the `storageId` to the add-file call. Builds, exports and reports are asynchronous and need a status poll
6. `/mts/{mtId}/translations` takes at most 100 strings a call and needs the `mt` scope and a configured engine

### TranslatePlus

1. Send the key as X-API-KEY; there is no read-only or scoped key
2. Use /v2/translate/batch for up to 100 texts instead of looping single calls
3. Keep each text under the plan's per-request character limit (500 on Free, up to 2,000 on Mega)
4. On 429 wait until X-RateLimit-Reset, then retry a few times at most
5. Don't rely on an SLA; the terms don't guarantee uptime

## Questions

### Which is better for AI agents, Crowdin or TranslatePlus?

Crowdin scores 69.6 (B) on agent readiness against TranslatePlus's 39.7 (E), and leads in 6 of 7 scored categories.

### Do Crowdin and TranslatePlus need an API key?

Crowdin takes an API key or an OAuth sign-in. TranslatePlus needs an API key.

### Can an agent call Crowdin and TranslatePlus without installing anything?

Crowdin has a hosted endpoint at https://api.crowdin.com/api/v2. No hosted endpoint is listed for TranslatePlus.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/crowdin-vs-translateplus.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crowdin-vs-translateplus.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "crowdin", "b": "translateplus"}`. From a terminal: `anchor compare crowdin translateplus`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crowdin.json and https://www.anchorterminal.com/api/v1/tools/translateplus.json

## Other comparisons with Crowdin or TranslatePlus

- [Amazon Translate vs Crowdin](https://www.anchorterminal.com/compare/amazon-translate-vs-crowdin.md)
- [Amazon Translate vs TranslatePlus](https://www.anchorterminal.com/compare/amazon-translate-vs-translateplus.md)
- [Azure Translator vs Crowdin](https://www.anchorterminal.com/compare/azure-translator-vs-crowdin.md)
- [Azure Translator vs TranslatePlus](https://www.anchorterminal.com/compare/azure-translator-vs-translateplus.md)
- [Crowdin vs DeepL API](https://www.anchorterminal.com/compare/crowdin-vs-deepl-api.md)
- [Crowdin vs Google Cloud Translation](https://www.anchorterminal.com/compare/crowdin-vs-google-cloud-translation.md)
- [Crowdin vs Lara Translate API](https://www.anchorterminal.com/compare/crowdin-vs-lara-translate.md)
- [Crowdin vs LibreTranslate](https://www.anchorterminal.com/compare/crowdin-vs-libretranslate.md)
- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)
- [Crowdin vs Lingvanex Translation API](https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.md)
- [Crowdin vs Localazy](https://www.anchorterminal.com/compare/crowdin-vs-localazy.md)
- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)
- [Crowdin vs Phrase](https://www.anchorterminal.com/compare/crowdin-vs-phrase.md)
- [Crowdin vs Smartcat](https://www.anchorterminal.com/compare/crowdin-vs-smartcat.md)
- [Crowdin vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/crowdin-vs-systran.md)
- [DeepL API vs TranslatePlus](https://www.anchorterminal.com/compare/deepl-api-vs-translateplus.md)
- [Google Cloud Translation vs TranslatePlus](https://www.anchorterminal.com/compare/google-cloud-translation-vs-translateplus.md)
- [Lara Translate API vs TranslatePlus](https://www.anchorterminal.com/compare/lara-translate-vs-translateplus.md)
- [LibreTranslate vs TranslatePlus](https://www.anchorterminal.com/compare/libretranslate-vs-translateplus.md)
- [Lingo.dev vs TranslatePlus](https://www.anchorterminal.com/compare/lingo-dev-vs-translateplus.md)
- [Lingvanex Translation API vs TranslatePlus](https://www.anchorterminal.com/compare/lingvanex-vs-translateplus.md)
- [Localazy vs TranslatePlus](https://www.anchorterminal.com/compare/localazy-vs-translateplus.md)
- [Lokalise vs TranslatePlus](https://www.anchorterminal.com/compare/lokalise-vs-translateplus.md)
- [Phrase vs TranslatePlus](https://www.anchorterminal.com/compare/phrase-vs-translateplus.md)
- [Smartcat vs TranslatePlus](https://www.anchorterminal.com/compare/smartcat-vs-translateplus.md)
- [SYSTRAN Translate API vs TranslatePlus](https://www.anchorterminal.com/compare/systran-vs-translateplus.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp