Lecto Translation API vs LibreTranslate API

Two free Text Analysis APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose Lecto Translation API if you want to call it from browser JavaScript, faster responses.
Choose LibreTranslate API if you want to start without an API key.

	Lecto Translation API	LibreTranslate API
What it does	Translation API with free tier and reasonable prices.	Translation tool with 17 available languages.
Provider	rapidapi.com	libretranslate.com
API key	Required	Not needed
HTTPS	Yes	Yes
CORS (browser calls)	Yes	Unknown
Status today	Online · 542 ms	Online · 1461 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

Translation API with free tier and reasonable prices.

Strengths

Translation tool with 17 available languages.

Strengths

Prototyping or a tutorial? Pick the one that needs no API key.
Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
Still unsure? Both are free to try: send one request to each and compare the data you get back.

Lecto Translation API requires an API key; LibreTranslate API doesn't, so LibreTranslate API is quicker to try.

Lecto Translation API supports CORS, so front-end JavaScript can call it directly. Call the other from a server.