GeoNet API vs LibreTranslate

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2533619
P95 · ms28081474
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

GeoNet API vs LibreTranslate: common questions

Which is more reliable, GeoNet API or LibreTranslate?

Both are neck-and-neck — GeoNet API and LibreTranslate each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, GeoNet API or LibreTranslate?

LibreTranslate has the lower median latency in our checks — GeoNet API responds in 2533 ms versus LibreTranslate at 619 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do GeoNet API and LibreTranslate need an API key?

Neither needs a paid key — GeoNet 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 GeoNet API and LibreTranslate from the browser?

Yes — both GeoNet 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 GeoNet API and LibreTranslate free for commercial use?

GeoNet 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.