Clockify API vs LibreTranslate

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree tier — API key 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

Clockify API vs LibreTranslate: common questions

Which is more reliable, Clockify API or LibreTranslate?

On our scheduled checks, LibreTranslate leads on measured uptime — Clockify 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 Clockify API and LibreTranslate need an API key?

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

Can I call Clockify API and LibreTranslate from the browser?

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

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