Grass Touch API vs Slack

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

Uptime · 30d
Uptime · 90d2.9%100%
Uptime · 30d5.0%100%
P50 · ms1701324
P95 · ms2338808
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 Slack: common questions

Which is more reliable, Grass Touch API or Slack?

On our scheduled checks, Slack leads on measured uptime — Grass Touch API at 2.9% versus Slack at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Grass Touch API or Slack?

Slack has the lower median latency in our checks — Grass Touch API responds in 1701 ms versus Slack at 324 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Grass Touch API and Slack need an API key?

Grass Touch API needs no key, while Slack 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 Slack from the browser?

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

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