shipapis
StarSubmit an APISubmit API

Disify vs LectServe

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

APIDisifyNEW—LectServeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
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

Disify vs LectServe: common questions

Which is more reliable, Disify or LectServe?

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

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

Can I call Disify and LectServe from the browser?

Only Disify 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 Disify and LectServe free for commercial use?

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