Head to head · Translation · October 2026 research run

DeepL API vs Lara Translate API

DeepL API scores 71 (BB) on agent readiness against Lara Translate API's 64.7 (B), and leads in 5 of 7 scored categories. Lara Translate API leads on reliability and payments & pricing. Both do translation.

Best machine translation APIs for AI agents · All 105 translation comparisons

Which one, for what

DeepL API BB

Best for Agents that need terminology control, formality and document layout kept, in European and Asian languages, and teams that want an MCP server today.

Ahead on

  • Schema & documentation, 95 against 74
  • Agent ergonomics, 83 against 77
  • Security & auth, 82 against 40
  • Transparency & trust, 81 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset

Lara Translate API B

Best for Agents that localise for one brand and need glossaries, translation memories and style instructions on every call, especially from an MCP client.

Ahead on

  • Reliability, 80 against 52
  • Payments & pricing, 60 against 45

Watch for

Texts may be used for model improvement unless a request sets noTrace

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth DeepL API +42

DeepL API 82

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Keys go only in the Authorization header since query and body auth were switched off in January and February 2026. API Key Permissions, GA on 24 June 2026, scope a key to chosen endpoints, the Admin API creates, labels and deactivates developer keys, and the hosted MCP signs in with OAuth (30). DeepL says paid-plan texts aren't used for training without consent, while free services may keep content for a limited time to train models. The privacy policy doesn't say which side API Developer keys fall on (15 of 20). Paid-plan texts are deleted once the job is done, document translation runs on DeepL's own infrastructure in the EEA (12 of 15). Usage reports by key and custom reporting tag, and a trace ID per call, but no audit log of key use found (10 of 15). security.txt PGP-signed and valid to 2026-12-01 per the 30 September check, a security@deepl.com address in the repositories and SOC 2 Type II claimed. No bug bounty found (15 of 20).

Lara Translate API 40

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines, as the other translation listings are read. An access key ID and secret that the SDKs use to sign each request, and OAuth with a Lara account on the hosted MCP. No key scopes found (20). The developer docs say requests run in Learning Mode by default, so text may be stored and used for model improvement, and Incognito is opted into per request with noTrace (5 of 20). Learning Mode stores translation and context texts for as long as needed to improve the model unless deletion is requested. Incognito keeps text in memory only, and account content is deleted within 90 days of cancellation (5 of 15). No audit log or per-call usage view found (0). laratranslate.com has no security.txt (404 on 2 November). Translated's trust centre lists ISO/IEC 27001:2022 (auditor named) and SOC 2 Type 1 with documents behind an access request, though its SOC 2 report entry says the Type I audit is still under way, and laratranslate.com's llms.txt states the ISO 27001:2022 certification. The trust centre links Translated's vulnerability disclosure policy, with safe harbour and rewards at Translated's discretion, but its scope lists translated.com, Matecat and Matesub, not Lara. Certifications alone take 10, as coinmarketcap-x402-api (10). 20 + 5 + 5 + 0 + 10 = 40.

Reliability Lara Translate API +28

DeepL API 52

Status page at status.deepl.com, which the changelog says became one combined page with an API view on 16 July 2026 (20). The page renders only in a browser, and /history, the Statuspage JSON path and an RSS feed all return the same empty application shell on 1 November, so we couldn't read its incidents. That's our limit, not a finding, but the rubric gives 5 for history we can't read (5). Request size limits are published (128 KiB a request, 16 KiB of headers) and plan character caps, and the error-handling guide says there is no fixed request-per-second figure because the service adjusts to load (5 of 15). 429 and 529 mean wait and resend, 456 means a usage limit was reached, and the guide says to retry 429 and 5xx with exponential backoff and jitter, to honour Retry-After when a response includes one and to log X-Trace-ID. It doesn't say which responses carry Retry-After, and document uploads take no idempotency key (12 of 15). No SLA found for self-serve plans (0). The text and document APIs are GA (10).

Lara Translate API 80

Atlassian Statuspage at status.laratranslate.com with Lara Translation API as its own component (20). Its history feed, read on 2 November, lists seven incidents, the latest on 16 January 2026, so the page posts incidents and none falls in the 90 days from 4 August (30). Rate limits published, 1,000 characters a second and 10,000 a month on the free tier, 10,000 characters a second on paid plans (15). No documented status code for a breached limit and no retry or backoff advice (0). The terms state a guaranteed uptime of 98 per cent or higher, with refunds at Translated's discretion, which is weaker than a credit schedule (5 of 10). The SDKs and hosted MCP are GA. The raw REST API is on request only (10). 20 + 30 + 15 + 0 + 5 + 10 = 80.

Schema & documentation DeepL API +21

DeepL API 95

OpenAPI 3 document (version 3.14.0, 45 paths on 1 November), synced from DeepL's docs to the DeepLcom/openapi repository (last sync 28 October 2026) and served at developers.deepl.com (25). llms.txt with 144 links and agent instructions, plus a keyless docs MCP server since 3 June 2026 (10). Operation descriptions say what each call does, and the docs say when to pick latency_optimized or quality_optimized, though not when to avoid an endpoint (15 of 20). Enums for formality, tag handling, model type and sentence splitting, with required fields marked (15). /v2/translate documents 11 response codes including 429, 456 and 529, with examples throughout (15). Versioned paths (v1, v2, v3) and a dated changelog (15).

Lara Translate API 74

No public OpenAPI. The official MCP server publishes typed JSON Schema inputs and output schemas on all 22 tools, which is the contract an agent sees (20 of 25). llms.txt with about 30 entries (10). Tool descriptions say to call list_glossaries or list_memories first to resolve names, to send one target language per call, and to add instructions only when needed (18 of 20). Inputs typed with ID formats (gls_*, mem_*), a maximum of 10 glossaries and 20-word instructions, but language codes are free strings (13 of 15). SDK examples, and the SDKs raise typed errors for authentication, quota and validation, but no error code list was found (8 of 15). No public API changelog. The MCP repository and package versions are the only dated record (5 of 15).

Transparency & trust DeepL API +19

DeepL API 81

Closed service with published terms, the MCP server and OpenAPI repository under MIT (15). The privacy policy and data security page agree that paid-plan texts are deleted after the job and not used for training without consent, but neither places API Developer keys (22 of 30). Dated deprecations in the changelog, query and body auth deprecated in November 2025 and cut off on 20 January 2026 after a brownout, /v2/languages deprecated on 18 May 2026 (18 of 20). EEA processing for documents and regional endpoints for some customers, but we didn't find a public sub-processor list outside the trust centre at trust.deepl.com (12 of 20).

Lara Translate API 62

Closed service under published terms, SDKs and MCP server under MIT (15). The terms describe Learning Mode storing texts to improve Lara's model, the developer docs say that's the default, and the privacy policy says some data isn't used for AI model training without making clear which. No retention period for Learning Mode texts (12 of 30). ModernMT's sunset is dated (keys work until 2026-12-31) with an endpoint map, and the terms promise 30 days' notice of material changes (15 of 20). The DPA points to a sub-processor and data location list we didn't open (10 of 20).

Payments & pricing Lara Translate API +15

DeepL API 45

No x402, MPP or L402 (0). The plan structure is public, but the per-character rates sit on a pricing page that renders only in a browser and that we couldn't read, so plan-only credit (10). API Developer gives 1,000,000 characters in total with no card, per the 30 September check (20). A person signs up in a browser for a key, and the hosted MCP needs a DeepL account login (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Lara Translate API 60

No x402, MPP or L402 (0). Per-million-character prices for Standard, Think and Prosa published in dollars and euros without a login (20). The Free plan includes 10,000 API characters a month with no credit card required (20). A person signs up in a browser, and the hosted MCP signs in with a Lara account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics DeepL API +6

DeepL API 83

API reading of the checklist. Responses carry the translation and detected language, with billed characters opt-in through show_billed_characters. The local MCP server has 13 compact tools, the hosted one up to 28 per DeepL's docs (22 of 25). Many strings per call up to 128 KiB, paging on style rules and translation memories, up to 5 glossaries a request (18 of 20). Errors carry a message, a code where available and a trace ID, and the docs say which codes to retry (20). Text translation is stateless with backoff guidance, but document jobs take no idempotency key and the MCP tools carry no readOnlyHint or destructiveHint annotations (10 of 20). Two required fields on translate, official SDKs for Python, Node.js and others, but a free key sent to the paid host fails (13 of 15).

Lara Translate API 77

MCP reading of the checklist. 22 tools, three for translation, detection and the language list, 8 for translation memories and 11 for glossaries, with no read-only subset or toolsets (15). Translate takes an array of text blocks with a translatable flag per block, but list tools show no paging controls (12 of 20). Since 2.0.0 tool failures come back as isError results with messages instead of protocol errors (15 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, with deletes, updates and imports marked destructive (20). Translate needs only text and a target, and SDKs exist for Python, Node.js, Java, PHP and Go (15).

Score by category

CategoryWeightDeepL APILara Translate APIEdge
Reliability16%5280Lara Translate API +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9574DeepL API +21
Agent ergonomics13%8377DeepL API +6
Security & auth14%8240DeepL API +42
Payments & pricing10%4560Lara Translate API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8783DeepL API +4
Transparency & trust7%8162DeepL API +19
Negative events≤15-3-3
TotalBB 71/100B 64.7/100

Facts side by side

FactDeepL APILara Translate API
KindHTTP APIHTTP API
VendorDeepLTranslated
Hosted endpointhttps://api.deepl.com/v2/translatehttps://mcp.laratranslate.com/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (MCP server)MIT (MCP server and SDKs)
Tools exposed1322
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-292026-10-28
Terms last updated2026-08-01no date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity117 stars, 328k npm/wk, 291k PyPI/wk97 stars, 29k npm/wk, 1.7k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

DeepL API

Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call. API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset.

Lara Translate API

Glossaries, translation memories, styles and instructions on every translate call, and no status incident posted since January 2026. Texts may be used for model improvement unless a request sets noTrace, and the Python SDK removed a model attribute in a patch release without notice.

Before you call either

DeepL API

  1. Match the host to the key. Keys ending :fx go to api-free.deepl.com, others to api.deepl.com
  2. Send the key in the Authorization: DeepL-Auth-Key header, since query and body keys now get 403
  3. Retry 429 and 529 with exponential backoff but stop on 456, which means the quota is spent
  4. Set tag_handling to html for markup so the tags survive and aren't billed
  5. Put a key-level usage limit on any key an agent holds, and scope it to the endpoints it needs
  6. Set input_conversion_options=version:1,json-placeholders:translate on JSON documents only if placeholders should be translated; they're kept verbatim by default

Lara Translate API

  1. Set noTrace on every request that carries private text, since storage for model improvement is the default
  2. Leave reasoning off unless the text needs it. It moves the call to Lara Think at $2,499 per million characters
  3. Resolve glossary and memory names to gls_* and mem_* IDs with the list tools before translating
  4. Send one target language per translate call
  5. Merge short documents, since each file bills at least 20,000 characters
  6. Set DO_NOT_TRACK=1 when running @translated/lara-mcp locally if usage metrics shouldn't leave the machine. Since 2.1.0 they are on by default

Questions

Which is better for AI agents, DeepL API or Lara Translate API?

DeepL API scores 71 (BB) on agent readiness against Lara Translate API's 64.7 (B), and leads in 5 of 7 scored categories. Lara Translate API leads on reliability and payments & pricing.

Do DeepL API and Lara Translate API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call DeepL API and Lara Translate API without installing anything?

Yes. DeepL API has a hosted endpoint at https://api.deepl.com/v2/translate and Lara Translate API at https://mcp.laratranslate.com/v1.

Other comparisons with DeepL API or Lara Translate API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.