Jobicy vs Namedays Calendar

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

Uptime · 30d
Uptime · 90d97.8%92.1%
Uptime · 30d96.7%98.3%
P50 · ms560536
P95 · ms25982749
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 58 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Jobicy vs Namedays Calendar: common questions

Which is more reliable, Jobicy or Namedays Calendar?

On our scheduled checks, Jobicy leads on measured uptime — Jobicy at 97.8% versus Namedays Calendar at 92.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, Jobicy or Namedays Calendar?

Namedays Calendar has the lower median latency in our checks — Jobicy responds in 560 ms versus Namedays Calendar at 536 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 Jobicy and Namedays Calendar need an API key?

Neither needs a paid key — Jobicy is callable with no signup, and Namedays Calendar is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Jobicy and Namedays Calendar from the browser?

Yes — both Jobicy and Namedays Calendar 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 Jobicy and Namedays Calendar free for commercial use?

Jobicy has unclear commercial terms, and Namedays Calendar 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.