Grass Touch API vs mailboxlayer

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

Uptime · 30d
Uptime · 90d2.9%100%
Uptime · 30d5.0%100%
P50 · ms1701316
P95 · ms23382634
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Grass Touch API vs mailboxlayer: common questions

Which is more reliable, Grass Touch API or mailboxlayer?

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

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

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

Neither sends browser-friendly CORS headers reliably, so call Grass Touch API and mailboxlayer from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Grass Touch API and mailboxlayer free for commercial use?

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