shipapis
StarSubmit an APISubmit API

LectServe vs Namedays Calendar

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

APILectServeDYING69Namedays CalendarHEALTHY89
Uptime · 30d
Uptime · 90d92.2%92.2%
Uptime · 30d76.7%98.3%
P50 · ms334263
P95 · ms16332749
Authnonenone
CORSnoyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 58 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

LectServe vs Namedays Calendar: common questions

Which is more reliable, LectServe or Namedays Calendar?

Both are neck-and-neck — LectServe and Namedays Calendar each measure 92.2% 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, LectServe or Namedays Calendar?

Namedays Calendar has the lower median latency in our checks — LectServe responds in 334 ms versus Namedays Calendar at 263 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 LectServe and Namedays Calendar need an API key?

Neither needs a paid key — LectServe 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 LectServe and Namedays Calendar from the browser?

Only Namedays Calendar is browser-friendly — it returns CORS headers over HTTPS. LectServe needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are LectServe and Namedays Calendar free for commercial use?

LectServe 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.