Church Calendar vs Jobvetta

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms59185
P95 · ms1997215
AuthnoneapiKey
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-07-25
operationalpartialdownno data

Church Calendar vs Jobvetta: common questions

Which is more reliable, Church Calendar or Jobvetta?

Both are neck-and-neck — Church Calendar and Jobvetta 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, Church Calendar or Jobvetta?

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

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

Can I call Church Calendar and Jobvetta from the browser?

Only Jobvetta 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 Jobvetta free for commercial use?

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