Grass Touch API vs mail.tm
Same instrument, two spec sheets — measured, not claimed.
Grass Touch API vs mail.tm: common questions
Which is more reliable, Grass Touch API or mail.tm?
On our scheduled checks, mail.tm leads on measured uptime — Grass Touch API at 2.9% versus mail.tm at 84.3% 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 mail.tm?
mail.tm has the lower median latency in our checks — Grass Touch API responds in 1701 ms versus mail.tm at 709 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 mail.tm need an API key?
Neither needs a paid key — Grass Touch API is callable with no signup, and mail.tm is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Grass Touch API and mail.tm from the browser?
Neither sends browser-friendly CORS headers reliably, so call Grass Touch API and mail.tm 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 mail.tm free for commercial use?
Grass Touch API has unclear commercial terms, and mail.tm 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.