shipapis
StarSubmit an APISubmit API

Church Calendar vs Ntropy Transaction API v1

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

APIChurch CalendarNEW—Ntropy Transaction API v1NEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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 Ntropy Transaction API v1: common questions

Which is more reliable, Church Calendar or Ntropy Transaction API v1?

On our scheduled checks, Ntropy Transaction API v1 leads on measured uptime — Church Calendar at —% versus Ntropy Transaction API v1 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 Ntropy Transaction API v1 need an API key?

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

Can I call Church Calendar and Ntropy Transaction API v1 from the browser?

Neither sends browser-friendly CORS headers reliably, so call Church Calendar and Ntropy Transaction API v1 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 Ntropy Transaction API v1 free for commercial use?

Church Calendar has unclear commercial terms, and Ntropy Transaction API v1 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.