# Lingvanex Translation API vs Localazy

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

- Canonical: https://www.anchorterminal.com/compare/lingvanex-vs-localazy
- Markdown: https://www.anchorterminal.com/compare/lingvanex-vs-localazy.md (~3,750 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

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: grade F, 37.3/100, rank #1376 of 1510. Markdown https://www.anchorterminal.com/tools/lingvanex.md · JSON https://www.anchorterminal.com/api/v1/tools/lingvanex.json
- Localazy: grade C, 54.4/100, rank #915 of 1510. Markdown https://www.anchorterminal.com/tools/localazy.md · JSON https://www.anchorterminal.com/api/v1/tools/localazy.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

### Lingvanex Translation API (F)

Good for: Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Product pages disagree on bulk and on-premise prices

### Localazy (C)

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 in its favour:
- Free to start without a card

Watch for: No OpenAPI spec, and llms.txt only lists top-level pages


## 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.

## Score by category

| Category | Weight | Lingvanex Translation API | Localazy | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 68 | Localazy +28 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 48 | 51 | Localazy +3 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 62 | Localazy +12 |
| Security & auth | 14% (17.5 this run) | 37 | 37 | even |
| Payments & pricing | 10% (12.5 this run) | 15 | 35 | Localazy +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 6 | 75 | Localazy +69 |
| Transparency & trust | 7% (8.8 this run) | 51 | 57 | Localazy +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **37.3 · F** | **54.4 · C** | |

## Facts side by side

| Fact | Lingvanex Translation API | Localazy |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Lingvanex | Localazy s.r.o. |
| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | Token |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-10-26 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2026-05-01 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 3 PyPI/wk | 61k npm/wk |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Lingvanex Translation API

- +0.3 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

### Localazy

No score change since it was listed.

## Verdicts

**Lingvanex Translation API.** $5 per million characters list price. Product pages disagree on bulk and on-premise prices.

**Localazy.** Localazy is a localisation platform whose REST API, CLI and AI Translation endpoint use project-scoped bearer tokens, with published limits, a free plan and a no-card trial. There's no OpenAPI spec, no 429 guidance, no security.txt or disclosure policy, and project tokens carry full read and write access.

## Before you call either

### Lingvanex Translation API

1. Call the https:// server, not the http:// one the spec also lists
2. Send `platform` as api on every call, since the spec marks it required
3. Use locale codes such as en_GB and de_DE, not two-letter codes
4. Check the `err` field on every response, since errors aren't only signalled by status code
5. Send an array in `data` to translate several strings in one call

### Localazy

1. Ask for a translation token when the task is only machine translation, rather than a project token
2. Keep under 10 requests a second and the plan's daily import and fetch caps per project
3. Use the Localazy CDN, not the API, to fetch translations in a live app
4. Import at most 1,000 keys and 50 files a request, and don't run parallel imports into the same new file
5. Check the account's credit balance before bulk AI translation, since each word uses credits

## Questions

### Which is better for AI agents, Lingvanex Translation API or Localazy?

Localazy scores 54.4 (C) on agent readiness against Lingvanex Translation API's 37.3 (F), and leads in 6 of 7 scored categories.

### Do Lingvanex Translation API and Localazy need an API key?

Lingvanex Translation API needs an API key. Localazy needs an access token.

### Can an agent call Lingvanex Translation API and Localazy without installing anything?

Lingvanex Translation API has a hosted endpoint at https://api-b2b.backenster.com/b1/api/v3. No hosted endpoint is listed for Localazy.


## For agents

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

## Other comparisons with Lingvanex Translation API or Localazy

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