AI Dev Jobs vs Church Calendar

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms339848
P95 · ms9411997
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — public read endpoints openFree — limits not published
Rate limitHourly abuse throttle; optional free API keyUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AI Dev Jobs vs Church Calendar: common questions

Which is more reliable, AI Dev Jobs or Church Calendar?

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

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

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

Can I call AI Dev Jobs and Church Calendar from the browser?

Only AI Dev Jobs 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 AI Dev Jobs and Church Calendar free for commercial use?

AI Dev Jobs has unclear commercial terms, and Church 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.