shipapis
StarSubmit an APISubmit API

Church Calendar vs Emailvalidation

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

APIChurch CalendarNEW—EmailvalidationNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Church Calendar vs Emailvalidation: common questions

Which is more reliable, Church Calendar or Emailvalidation?

On our scheduled checks, Emailvalidation leads on measured uptime — Church Calendar at —% versus Emailvalidation at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Church Calendar and Emailvalidation need an API key?

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

Can I call Church Calendar and Emailvalidation from the browser?

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

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