Lingvanex Translation API by Lingvanex

# Fix list: Lingvanex Translation API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/lingvanex, the October 2026 research run, assessed 1 October 2026. Grade F, 37.2 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Lingvanex Translation API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 40 out of 100, up to 12 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Security & auth, 37 out of 100, up to 11 more on the total

Why it scored 37: Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. A bearer key from the account panel, no scopes or rotation found (20), less 5 because the OpenAPI document lists an http:// server beside the https:// one, so the key can be sent in clear text (15). The product page says translated data isn't used to train models, but the privacy policy doesn't say so and lists OpenAI and Anthropic among more than 30 recipients without saying which receive API text (15 of 20). The product page says data is deleted immediately after translation, the privacy policy says API documents and responses are deleted within 24 to 72 hours, and the API terms say content is stored only as far as technically required (7 of 15). Lingvanex keeps access logs for billing and security, and no customer-facing per-call log was found (0). security.txt couldn't be fetched (robots.txt), and no disclosure policy or certification found (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Payments & pricing, 15 out of 100, up to 10.6 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 4. Schema & documentation, 48 out of 100, up to 8.5 more on the total

Why it scored 48: OpenAPI 3.0.3 document on SwaggerHub with two paths, `/getLanguages` and `/translate` (25). No llms.txt per the 30 September check (0). Operation descriptions are one line and don't say when to use HTML mode or transliteration (5 of 20). `translateMode` is an enum and required fields are marked, but `platform` is a required field with one fixed value and `data` is a string or array (8 of 15). Only 200 and 403 are documented, and errors come back in an `err` string field (5 of 15). A v3 path and spec version 1.0.0, no changelog found (5 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 5. Maintenance & community, 6 out of 100, up to 8.2 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 6. Agent ergonomics, 50 out of 100, up to 8.1 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 7. Transparency & trust, 50 out of 100, up to 4.4 more on the total

Made of editorial 38, provenance 61.

Why it scored 50: 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: lingvanex.com, registered 2016-12-28 (9 years) (11 of 15)
- Endpoint on the vendor's domain: api-b2b.backenster.com is not on lingvanex.com (0 of 15)
- Changelog: not found (0 of 10)
- security.txt: could not be fetched (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- The listing said no status page. We found a Better Stack page at status.lingvanex.com and the patch adds it to provenance.
- unchecked: the incident list behind the 99.934 per cent uptime figure, which the status page doesn't show.
- unchecked: whether API text reaches any of the AI vendors the privacy policy lists as recipients.
- unchecked: the developer docs at docs.lingvanex.com, which render only in a browser.

## Weaknesses

- Product pages disagree on bulk and on-premise prices
- The product page, privacy policy and API terms disagree on how long text is kept
- No published rate limits, and the terms let Lingvanex set them at its discretion
- No glossary or formality parameters, and only 200 and 403 documented
- No changelog, and the Python SDK hasn't changed since June 2024

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

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

## What the review panel asked for

- Reconcile the volume prices
- State the trial amount
- one retention statement
- document error codes

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.