Ntropy Transaction API v1 vs TimeZones iCal Library

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

Uptime · 30d
Uptime · 90d98.0%100%
Uptime · 30d96.7%100%
P50 · ms1223337
P95 · ms4484714
Authnonenone
CORSnoyes
HTTPSyesyes
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

Ntropy Transaction API v1 vs TimeZones iCal Library: common questions

Which is more reliable, Ntropy Transaction API v1 or TimeZones iCal Library?

On our scheduled checks, TimeZones iCal Library leads on measured uptime — Ntropy Transaction API v1 at 98.0% versus TimeZones iCal Library at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Ntropy Transaction API v1 or TimeZones iCal Library?

TimeZones iCal Library has the lower median latency in our checks — Ntropy Transaction API v1 responds in 1223 ms versus TimeZones iCal Library at 337 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 Ntropy Transaction API v1 and TimeZones iCal Library need an API key?

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

Can I call Ntropy Transaction API v1 and TimeZones iCal Library from the browser?

Only TimeZones iCal Library is browser-friendly — it returns CORS headers over HTTPS. Ntropy Transaction API v1 needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Ntropy Transaction API v1 and TimeZones iCal Library free for commercial use?

Ntropy Transaction API v1 has unclear commercial terms, and TimeZones iCal Library 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.