shipapis
StarSubmit an APISubmit API

Lanyard vs mail.tm

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

APILanyardHEALTHY75mail.tmHEALTHY82
Uptime · 30d
Uptime · 90d99.02%84.3%
Uptime · 30d100%75.0%
P50 · ms279709
P95 · ms15882351
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree — temporary mailboxes
Rate limitUnpublishedRate limited (429 on exceed); exact policy per docs.mail.tm
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs mail.tm: common questions

Which is more reliable, Lanyard or mail.tm?

On our scheduled checks, Lanyard leads on measured uptime — Lanyard at 99.02% 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, Lanyard or mail.tm?

Lanyard has the lower median latency in our checks — Lanyard responds in 279 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 Lanyard and mail.tm need an API key?

Neither needs a paid key — Lanyard 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 Lanyard and mail.tm from the browser?

Only Lanyard is browser-friendly — it returns CORS headers over HTTPS. mail.tm needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Lanyard and mail.tm free for commercial use?

Lanyard 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.