Grass Touch API vs Kickbox

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

Uptime · 30d
Uptime · 90d2.9%100%
Uptime · 30d5.0%100%
P50 · ms1701592
P95 · ms23383630
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — open disposable-address check
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Grass Touch API vs Kickbox: common questions

Which is more reliable, Grass Touch API or Kickbox?

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

Kickbox has the lower median latency in our checks — Grass Touch API responds in 1701 ms versus Kickbox at 592 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 Kickbox need an API key?

Neither needs a paid key — Grass Touch API is callable with no signup, and Kickbox is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

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