shipapis
StarSubmit an APISubmit API

Landing.jobs vs LectServe

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

APILanding.jobsNEW—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

Landing.jobs vs LectServe: common questions

Which is more reliable, Landing.jobs or LectServe?

On our scheduled checks, LectServe leads on measured uptime — Landing.jobs 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 Landing.jobs and LectServe need an API key?

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

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

Landing.jobs 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.