shipapis
StarSubmit an APISubmit API

Lanyard vs mail.tm

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

APILanyardNEW—mail.tmNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
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, mail.tm leads on measured uptime — Lanyard at —% versus mail.tm at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

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?

Yes — both Lanyard and mail.tm send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

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.