3 modes for the translation endpoint

25 July 2026
The translate endpoint now has three independent toggles: live, proofread, and humanizer. Each is billed separately, and you're only charged for the passes that actually run.

We've removed the old fast and deep tiers. Every translation on the Linguin API now starts with a single base pass, and you can enable only the extra processing your text needs.

{
  "text": "J'ai la flemme de me battre",
  "from": "fr",
  "to": "en",
  "live": true,
  "proofread": false,
  "humanizer": false
}

live

live works before translation begins. It scans the source text for slang, idioms, and other expressions that shouldn't be translated at face value. When it finds one, it looks up the meaning and translates the text using that context.

It's most useful for informal writing where literal translation often misses the intended meaning.

proofread

proofread runs after the translation is complete.

It reviews wording that could reasonably be translated in more than one way, compares it against the strongest alternatives, and checks how those alternatives are actually used in real writing. If the evidence favors a different choice, it replaces the original wording.

This works best for formal or professional writing, where translated text can sometimes retain awkward source language phrasing.

humanizer

humanizer is the final optional pass. It rewrites the translated text so it reads more naturally and less like machine-generated output, while preserving the original meaning.

Billing

Every response includes a list of the passes that actually ran, and you're billed only for those passes.

For example, if live is enabled but doesn't find anything worth looking up, it won't run. It won't appear in the response, and you won't be charged for it.

The legacy mode parameter is still accepted for backward compatibility, but it no longer has any effect.

See the pricing page for the cost of each toggle, and the documentation for the complete request format.

Look up word or phrase...