shipapis
StarSubmit an APISubmit API

Landing.jobs vs Disify

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

APILanding.jobsUNMONITORED—DisifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
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

Landing.jobs vs Disify: common questions

Which is more reliable, Landing.jobs or Disify?

Only Disify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Landing.jobs and Disify need an API key?

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

Can I call Landing.jobs and Disify from the browser?

Yes — both Landing.jobs and Disify send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Landing.jobs and Disify free for commercial use?

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