caldays vs Landing.jobs

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

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

caldays vs Landing.jobs: common questions

Which is more reliable, caldays or Landing.jobs?

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

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

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

Yes — both caldays and Landing.jobs 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 caldays and Landing.jobs free for commercial use?

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