Free Jobs API vs Open Topo Data

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

Uptime · 30d
Uptime · 90d98.0%93.1%
Uptime · 30d98.3%88.3%
P50 · ms833285
P95 · ms4763573
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Free Jobs API vs Open Topo Data: common questions

Which is more reliable, Free Jobs API or Open Topo Data?

On our scheduled checks, Free Jobs API leads on measured uptime — Free Jobs API at 98.0% versus Open Topo Data at 93.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Free Jobs API or Open Topo Data?

Open Topo Data has the lower median latency in our checks — Free Jobs API responds in 833 ms versus Open Topo Data at 285 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 Free Jobs API and Open Topo Data need an API key?

Neither needs a paid key — Free Jobs API is callable with no signup, and Open Topo Data is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Free Jobs API and Open Topo Data from the browser?

Neither sends browser-friendly CORS headers reliably, so call Free Jobs API and Open Topo Data from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Free Jobs API and Open Topo Data free for commercial use?

Free Jobs API has unclear commercial terms, and Open Topo Data 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.