shipapis
StarSubmit an APISubmit API

Hunter vs LibreTranslate

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

APIHunterHEALTHY96LibreTranslateHEALTHY92
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362619
P95 · ms8591474
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree tier — key may be requiredFree — /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

Hunter vs LibreTranslate: common questions

Which is more reliable, Hunter or LibreTranslate?

Both are neck-and-neck — Hunter 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, Hunter or LibreTranslate?

Hunter has the lower median latency in our checks — Hunter responds in 362 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 Hunter and LibreTranslate need an API key?

LibreTranslate needs no key, while Hunter requires a free API key. If you want to start calling without signup, reach for LibreTranslate first.

Can I call Hunter and LibreTranslate from the browser?

Only LibreTranslate is browser-friendly — it returns CORS headers over HTTPS. Hunter needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Hunter and LibreTranslate free for commercial use?

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