Church Calendar vs Jobicy

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms848629
P95 · ms19972417
Authnonenone
CORSyesyes
HTTPSnoyes
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

Church Calendar vs Jobicy: common questions

Which is more reliable, Church Calendar or Jobicy?

On our scheduled checks, Church Calendar leads on measured uptime — Church Calendar at 100% versus Jobicy at 99.02% 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, Church Calendar or Jobicy?

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

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

Can I call Church Calendar and Jobicy from the browser?

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

Are Church Calendar and Jobicy free for commercial use?

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