shipapis
StarSubmit an APISubmit API

Emailvalidation vs LectServe

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

APIEmailvalidationNEW—LectServeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Emailvalidation vs LectServe: common questions

Which is more reliable, Emailvalidation or LectServe?

On our scheduled checks, LectServe leads on measured uptime — Emailvalidation at —% versus LectServe 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 Emailvalidation and LectServe need an API key?

LectServe needs no key, while Emailvalidation requires a free API key. If you want to start calling without signup, reach for LectServe first.

Can I call Emailvalidation and LectServe from the browser?

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

Are Emailvalidation and LectServe free for commercial use?

Emailvalidation has unclear commercial terms, and LectServe 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.