Church Calendar vs Public Time API
Same instrument, two spec sheets — measured, not claimed.
Church Calendar vs Public Time API: common questions
Which is more reliable, Church Calendar or Public Time API?
Both are neck-and-neck — Church Calendar and Public Time API 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 Public Time API?
Public Time API has the lower median latency in our checks — Church Calendar responds in 848 ms versus Public Time API at 242 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 Public Time API need an API key?
Neither needs a paid key — Church Calendar is callable with no signup, and Public Time API is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Church Calendar and Public Time API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Church Calendar and Public Time API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Church Calendar and Public Time API free for commercial use?
Church Calendar has unclear commercial terms, and Public Time API 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.