shipapis
StarSubmit an APISubmit API

LectServe vs Public Time API

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

APILectServeNEW—Public Time APINEW—
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

LectServe vs Public Time API: common questions

Which is more reliable, LectServe or Public Time API?

On our scheduled checks, Public Time API leads on measured uptime — LectServe at —% versus Public Time API 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 LectServe and Public Time API need an API key?

Neither needs a paid key — LectServe is callable with no signup, and Public Time API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call LectServe and Public Time API from the browser?

Neither sends browser-friendly CORS headers reliably, so call LectServe and Public Time API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are LectServe and Public Time API free for commercial use?

LectServe has unclear commercial terms, and Public Time API 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.