Grass Touch API vs Landing.jobs

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
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

Grass Touch API vs Landing.jobs: common questions

Which is more reliable, Grass Touch API or Landing.jobs?

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

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

Only Landing.jobs is browser-friendly — it returns CORS headers over HTTPS. Grass Touch API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Grass Touch API and Landing.jobs free for commercial use?

Grass Touch API 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.