# Lingvanex Translation API vs TranslatePlus (slim)

> TranslatePlus scores 39.7 (E) 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-translateplus.md (~3,250 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/lingvanex-vs-translateplus.json · canonical https://www.anchorterminal.com/compare/lingvanex-vs-translateplus
- 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)

TranslatePlus scores 39.7 (E) 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
- TranslatePlus: E 39.7, rank #1335 of 1510 · https://www.anchorterminal.com/tools/translateplus.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; No incidents deducted, where TranslatePlus loses 3 points for them.
- TranslatePlus, good for Low-cost per-request translation of short strings, HTML, emails, subtitles and i18n files for small projects. Ahead on Reliability, 45 against 40; Agent ergonomics, 61 against 50; Payments & pricing, 30 against 15.

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

| Fact (where they differ) | Lingvanex Translation API | TranslatePlus |
| --- | --- | --- |
| Vendor | Lingvanex | PetaBytes, Inc. |
| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | no (local only) |
| Pricing | Pay per use | Freemium |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | none | 2026-01-11 |
| Terms last updated | no date given | 2024-12-18 |
| Privacy policy last updated | 2026-05-01 | no date given |
| Popularity | 3 PyPI/wk | 6 npm/wk, 4 PyPI/wk |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Payments & pricing, TranslatePlus +15: 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).); TranslatePlus 30 (No x402, MPP or L402 (0). Per-request prices public, $0.001 a request after the free tier and $0.0001 to $0.0002 on the $49, $99 and $299 monthly plans (20). Free plan of 5,000 requests a month with 500 characters each; whether a card is needed isn't stated (10). A person signs up in a browser or with Google OAuth (0). 0+20+10+0 = 30.)
- Agent ergonomics, TranslatePlus +11: 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).); 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.)
- Reliability, TranslatePlus +5: 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).); 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.)