Grass Touch API vs xfetch

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Grass Touch API vs xfetch: common questions

Which is more reliable, Grass Touch API or xfetch?

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

Grass Touch API needs no key, while xfetch requires a free API key. If you want to start calling without signup, reach for Grass Touch API first.

Can I call Grass Touch API and xfetch from the browser?

Only xfetch 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 xfetch free for commercial use?

Grass Touch API has unclear commercial terms, and xfetch 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.