# Localazy vs SYSTRAN Translate API (slim)

> Localazy scores 54.4 (C) to SYSTRAN Translate's 40.2 (E) for translation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/localazy-vs-systran.md (~4,750 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/localazy-vs-systran.json · canonical https://www.anchorterminal.com/compare/localazy-vs-systran
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Localazy scores 54.4 (C) on agent readiness against SYSTRAN Translate API's 40.2 (E), and leads in 5 of 7 scored categories. SYSTRAN Translate API leads on security & auth and payments & pricing. Both do translation.

- Localazy: C 54.4, rank #909 of 1486 · https://www.anchorterminal.com/tools/localazy.min.md
- SYSTRAN Translate API: E 40.2, rank #1305 of 1486 · https://www.anchorterminal.com/tools/systran.min.md
- Localazy, good for App and game teams that keep source strings in a TMS and want agents to push keys, pull translations or run AI translation with a glossary. Ahead on Reliability, 68 against 25; Schema & documentation, 51 against 42; Agent ergonomics, 62 against 54; Maintenance & community, 75 against 4.
- SYSTRAN Translate API, good for Teams that want European Union hosting, user dictionaries and translation memories applied through profiles, or the same API on an on-premises SYSTRAN server. Ahead on Security & auth, 55 against 37; Payments & pricing, 40 against 35. Also A hosted endpoint, with nothing to install.

| Category | Localazy | SYSTRAN Translate API |
| --- | --- | --- |
| Reliability (16%) | 68 | 25 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 51 | 42 |
| Agent ergonomics (13%) | 62 | 54 |
| Security & auth (14%) | 37 | 55 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 4 |
| Transparency & trust (7%) | 57 | 53 |

| Fact (where they differ) | Localazy | SYSTRAN Translate API |
| --- | --- | --- |
| Vendor | Localazy s.r.o. | SYSTRAN (ChapsVision) |
| Hosted endpoint | no (local only) | `https://api-translate.systran.net` |
| Auth | Token | OAuth or key |
| Pricing | Freemium | Pay per use |
| Licence | none | Proprietary service under the SYSTRAN Translate PRO terms and conditions |
| llms.txt | yes | no |
| Last release | 2026-10-26 | 2023-06-16 |
| Privacy policy last updated | no date given | no document linked |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 61k npm/wk | none |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Maintenance & community, Localazy +71: Localazy 75 (@localazy/api-client 2.3.2 on 26 October 2026 (30). Releases 2.3.0 (12 August), 2.3.1 (29 September) and 2.3.2 (26 October) in the last 90 days (20). Support by email, blog release updates, and public GitHub repositories, but we didn't read issue reply times (7). The TypeScript client and the CLI (2.0.12 on 31 July 2026) are current (13). The client repository shows coverage badges; we didn't confirm CI runs (5). 30+20+7+13+5 = 75.); SYSTRAN Translate API 4 (No changelog or release notes for the API were found. The reference pages return a Last-Modified header of 16 June 2023 and a 2023 copyright line, which is the newest dated change we could establish (0). No dated entries in the last 90 days (0). Support runs through contact forms and a help centre at help.systrangroup.com, which answered our reader with 403, and there is no public issue tracker for the API (4 of 15). No official SDK was found. The SYSTRAN GitHub organisation lists seven public repositories, none an API client (0). No package to assess (0). Total 4.)
- Reliability, Localazy +43: Localazy 68 (Hosted lines, for the REST API at api.localazy.com. Better Stack status page with Web, API, Public API, Payments and Connect API components and 30, 60 and 90-day uptime (20). The incidents page reports none for September, October or November 2026, but the Public API shows 99.805% uptime in one 30-day bucket, roughly an hour and a half of downtime with no incident posted, so the line is held below clean (25). Limits per plan of 100 requests a minute and 10 a second, plus daily import and fetch caps per project (15). No 429 or retry guidance found in the API docs (0). No SLA found on the pricing page or in the terms (0). The core API is GA; the AI Translation endpoint is marked beta (8). 20+25+15+0+0+8 = 68.); SYSTRAN Translate API 25 (Hosted reading of the checklist. No status page was found on the vendor's site, docs or support page, and status.systran.net and status.systransoft.com did not resolve (0). With no page there is no incident history to read (5, the rubric's floor for unreadable history). Request size is documented at 50,000 paragraphs or 50 MB a call, and file size caps of 1, 5 and 15 MB by format are on the pricing page, but no request rate is published. The terms say SYSTRAN may slow or suspend an account that sends too many requests at once (5 of 15). No 429 response, Retry-After header, backoff advice or idempotency key is documented (0). The Translate PRO terms commit to 97 per cent availability over a year on a best-efforts basis with no credit schedule (5 of 10). The API is generally available (10). Total 25.)
- Security & auth, SYSTRAN Translate API +18: Localazy 37 (Bearer tokens in the Authorization header. A project token reaches every endpoint of one project with read and write access; a translation token reaches only the AI Translation endpoint; organisation tokens are in beta on request (20). The translation token is the only least-privilege option, and project tokens can delete keys and glossary items without a confirmation step (10). The API returns strings written by translators and contributors, with no guidance on untrusted content (5). No per-call log or audit trail for tokens found (2). localazy.com/.well-known/security.txt and /security return 404, and we found no disclosure policy or certification (0). 20+10+5+2+0 = 37.); SYSTRAN Translate API 55 (Model reading of the checklist, as for the other translation listings, with training and retention in place of the least-privilege and injection lines. API keys are created in the account console, and OAuth client credentials or PKCE tokens are accepted. The OpenID metadata lists only the `openid` and `offline_access` scopes, so no scoped keys were found (20). The key is also accepted as a `?key=` query parameter (minus 10). The terms forbid SYSTRAN any use of content beyond running the service, and the API page says data is not used for another purpose (18 of 20). Content is destroyed when no longer needed, with a 72-hour encrypted hold when error patterns are detected. Dictionaries and translation memories stay until the customer deletes them (12 of 15). An administrator's usage dashboard groups consumption by user agent. No audit log was found (5 of 15). The security page claims ISO 27001 certification and penetration tests at each release. No security.txt, disclosure policy or bug bounty was found (10 of 20). Total 55.)
- Schema & documentation, Localazy +9: Localazy 51 (No OpenAPI or other machine-readable contract was found (0). localazy.com/llms.txt is a six-link index of top-level pages, with no Markdown docs for agents (5). Each endpoint page states which token types can call it, whether write permission is needed and the minimum role, and the limits page says to use the CDN, not the API, for production fetches (14). Request bodies list required and optional fields with limits, such as 512 characters for a key and 1,000 for a comment (12). Sample requests, responses and error responses per endpoint (13). Docs pages carry 'last updated' dates and the blog posts dated release updates, but there's no API version or changelog (7). 0+5+14+12+13+7 = 51.); SYSTRAN Translate API 42 (The five reference pages are generated from Swagger definitions and show typed parameters and 60 operations, but no OpenAPI or Swagger file is linked for download, so an agent has only HTML (8 of 25). No llms.txt at docs.systran.net or www.systransoft.com, both 404 (0). Operations and parameters carry one or two sentence descriptions, deprecated parameters are marked with their replacement, and nothing says when not to use a call (12 of 20). Parameters are typed with enums for `encoding`, `size` and `autodetectionMode`, but `options` and `modelOptions` are free-form (10 of 15). Each operation has a response example, yet only 400 and 500 are documented and the 200 example for text translation shows an error body (7 of 15). Each API states a version (Translation 2.11.0, Profiles 1.8.0) and has an `apiVersion` endpoint, with no changelog found (5 of 15). Total 42.)
- Agent ergonomics, Localazy +8: Localazy 62 (API reading. List endpoints return whole projects, files and keys with few output controls (13). Filtering by file, language and tags, and batch imports of up to 1,000 keys and 50 files a request (14). Error responses are documented per endpoint, with HTTP codes and messages (12). No idempotency keys, and the docs warn against parallel imports into the same new file (8). Official TypeScript API client, a CLI and Android and iOS libraries, with few required fields (15). 13+14+12+8+15 = 62.); SYSTRAN Translate API 54 (API reading of the checklist. Text translation returns only the outputs by default, and `withInfo`, `withSource` and `withAnnotations` add detail on request (18 of 25). Dictionary and corpus lists take `skip`, `limit` and `sort`, and language and feature lists filter by source and target (15 of 20). Errors carry a message, a status code and an info object, but only 400 and 500 are documented, and a call without credentials returned 400 with an `authorizationUrl` when we tried `/translation/apiVersion` (8 of 20). No idempotency key or retry guidance. File jobs return a `requestId` that can be polled and cancelled (5 of 20). Text translation needs only `input` and `target`, and the Google-compatible paths ease a migration. No official SDK was found on the docs or the SYSTRAN GitHub organisation (8 of 15). Total 54.)
- Payments & pricing, SYSTRAN Translate API +5: Localazy 35 (No x402, MPP or L402 (0). Plan prices are public ($34, $78 and $175 a month billed annually) and credits are $1 each, with Localazy AI at about $0.005 a word on average, so partial per-unit credit (15). A free plan for small projects and a 14-day Business trial with no credit card (20). A person signs up in a browser and mints tokens in the developer settings (0). 0+15+20+0 = 35.); SYSTRAN Translate API 40 (No x402, MPP or L402 (0). The developer pricing page shows €14.99 for 1 million characters, billed monthly, without a login. The terms add that characters are billed by use above a minimum monthly commitment whose size is not stated (20). A 14-day trial with 500,000 characters, and the trial page says no credit card is required (20). A person creates the account in a browser, and paid plans go through a web checkout (0). Total 40.)