shipapis
StarSubmit an APISubmit API

Ntropy Transaction API v1 vs Namedays Calendar

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

APINtropy Transaction API v1NEW—Namedays CalendarNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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 Namedays Calendar: common questions

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

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

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

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

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

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