shipapis
StarSubmit an APISubmit API

eLife Sciences API vs LibreTranslate

Same instrument, two spec sheets — measured, not claimed.

APIeLife Sciences APINEW—LibreTranslateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree — limits not publishedFree — /languages is keyless; hosted /translate may require a key or donation
Rate limitUnpublishedUnpublished (per hosted instance)
In directory since2026-07-052026-07-05
operationalpartialdownno data

eLife Sciences API vs LibreTranslate: common questions

Which is more reliable, eLife Sciences API or LibreTranslate?

On our scheduled checks, LibreTranslate leads on measured uptime — eLife Sciences API at —% versus LibreTranslate at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do eLife Sciences API and LibreTranslate need an API key?

Neither needs a paid key — eLife Sciences API is callable with no signup, and LibreTranslate is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call eLife Sciences API and LibreTranslate from the browser?

Yes — both eLife Sciences API and LibreTranslate send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are eLife Sciences API and LibreTranslate free for commercial use?

eLife Sciences API has unclear commercial terms, and LibreTranslate has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.