# Lingvanex Translation API vs Localazy (slim)

> Localazy scores 54.4 (C) to Lingvanex Translation's 37.3 (F) for translation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/lingvanex-vs-localazy.md (~3,750 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/lingvanex-vs-localazy.json · canonical https://www.anchorterminal.com/compare/lingvanex-vs-localazy
- 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 Lingvanex Translation API's 37.3 (F), and leads in 6 of 7 scored categories. Both do translation.

- Lingvanex Translation API: F 37.3, rank #1376 of 1510 · https://www.anchorterminal.com/tools/lingvanex.min.md
- Localazy: C 54.4, rank #915 of 1510 · https://www.anchorterminal.com/tools/localazy.min.md
- Lingvanex Translation API, good for Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later. Also A hosted endpoint, with nothing to install.
- 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 40; Agent ergonomics, 62 against 50; Payments & pricing, 35 against 15; Maintenance & community, 75 against 6; Transparency & trust, 57 against 51. Also Free to start without a card.

| Category | Lingvanex Translation API | Localazy |
| --- | --- | --- |
| Reliability (16%) | 40 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 48 | 51 |
| Agent ergonomics (13%) | 50 | 62 |
| Security & auth (14%) | 37 | 37 |
| Payments & pricing (10%) | 15 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 6 | 75 |
| Transparency & trust (7%) | 51 | 57 |

| Fact (where they differ) | Lingvanex Translation API | Localazy |
| --- | --- | --- |
| Vendor | Lingvanex | Localazy s.r.o. |
| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | no (local only) |
| Auth | API key | Token |
| Pricing | Pay per use | Freemium |
| llms.txt | no | yes |
| Last release | none | 2026-10-26 |
| Privacy policy last updated | 2026-05-01 | no date given |
| Popularity | 3 PyPI/wk | 61k npm/wk |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Maintenance & community, Localazy +69: Lingvanex Translation API 6 (No dated API change, release note or changelog found (0). Nothing dated in the last 90 days (0). Support contact on the site, no public changelog or issue tracker found (3 of 15). The only SDK is the Python package 0.0.11 from 2024-06-24 (3 of 15). No public CI (0).); 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.)
- Reliability, Localazy +28: Lingvanex Translation API 40 (Better Stack status page at status.lingvanex.com with one Cloud API component and uptime bars for 30, 60 and 90 days (20). It shows 99.934 per cent uptime over 90 days, about 85 minutes down by its own measure, but lists no incidents, so we can't tell one outage over an hour from several short ones. We score it between the minor and one-major tiers (10). No rate limits published. The API terms say Lingvanex sets limits at its sole discretion (0). The OpenAPI document lists only 200 and 403, with no 429 or retry guidance (0). Under the terms the APIs come as is, with availability disclaimed, so no SLA (0). The cloud API isn't marked beta (10).); 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.)
- Payments & pricing, Localazy +20: Lingvanex Translation API 15 (No x402, MPP or L402 (0). $5 per million characters is published, but the two product pages give different volume prices, $3 per million for a 1 billion pre-purchase on one and $1 per million above 20 million on the other (15 of 20). A free trial is advertised with no amount, and both pages put a payment method before the API key (0). A person signs up in a browser (0).); 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.)
- Agent ergonomics, Localazy +12: Lingvanex Translation API 50 (API reading of the checklist. Responses carry the result and optional transliteration and nothing else (20 of 25). `data` takes an array of strings, but no request size limit is published (10 of 20). Errors are an `err` string and a 403, with no codes to act on (5 of 20). Translation is stateless, but there's no retry guidance (10 of 20). Locale codes such as en_GB rather than two-letter codes, a required `platform` value, and one SDK, Python 0.0.11 from June 2024 (5 of 15).); 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.)
- Transparency & trust, Localazy +6: Lingvanex Translation API 51 (Closed service under API terms that name Nordicwise Limited of Larnaca, Cyprus, but carry no date or governing law (10 of 15). Three data statements disagree on how long text is kept, immediately deleted, 24 to 72 hours, or as long as technically required (8 of 30). The API terms promise 4 weeks' written notice before a deprecated version is switched off (10 of 20). The privacy policy, updated 1 May 2026, lists more than 30 recipients including Google, Amazon Web Services, Cloudflare, Stripe, OpenAI and Anthropic, without data locations or which ones see API text (10 of 20).); Localazy 57 (Editorial half only. Closed service under terms that name Localazy s.r.o. of Brno and Czech law; the CLI is BSD-3-Clause and the API client MIT (15). The privacy policy keeps data while the service is used and 24 months after, and includes a DPA, but says nothing on whether content sent to Localazy AI is used for training (15). No deprecation policy or dated notices found (0). The DPA links a list of suppliers and subprocessors on an external knowledge base we didn't read (10). 15+15+0+10 = 40.)