shipapis
StarSubmit an APISubmit API

FinSignals API vs mail.tm

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

APIFinSignals APIHEALTHY96mail.tmHEALTHY82
Uptime · 30d
Uptime · 90d100%84.3%
Uptime · 30d100%75.0%
P50 · ms312709
P95 · ms14192351
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — temporary mailboxes
Rate limitUnpublishedRate limited (429 on exceed); exact policy per docs.mail.tm
In directory since2026-07-052026-07-05
operationalpartialdownno data

FinSignals API vs mail.tm: common questions

Which is more reliable, FinSignals API or mail.tm?

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

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

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

Only FinSignals API 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 FinSignals API and mail.tm free for commercial use?

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