shipapis
StarSubmit an APISubmit API

MailCheck.ai vs Public Time API

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

APIMailCheck.aiHEALTHY93Public Time APIHEALTHY98
Uptime · 30d
Uptime · 90d93.1%100%
Uptime · 30d93.3%100%
P50 · ms272242
P95 · ms842382
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit5 req/window · 4 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

MailCheck.ai vs Public Time API: common questions

Which is more reliable, MailCheck.ai or Public Time API?

On our scheduled checks, Public Time API leads on measured uptime — MailCheck.ai at 93.1% versus Public Time API 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, MailCheck.ai or Public Time API?

Public Time API has the lower median latency in our checks — MailCheck.ai responds in 272 ms versus Public Time API at 242 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 MailCheck.ai and Public Time API need an API key?

Neither needs a paid key — MailCheck.ai is callable with no signup, and Public Time API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call MailCheck.ai and Public Time API from the browser?

Only MailCheck.ai is browser-friendly — it returns CORS headers over HTTPS. Public Time API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are MailCheck.ai and Public Time API free for commercial use?

MailCheck.ai has unclear commercial terms, and Public Time API 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.