LectServe vs Nexmo API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms786567
P95 · ms16331221
AuthnoneapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished10, 120;w=60;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-120-rpm|remote_address", 10;w=1;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-10-rps|remote_address" req/window · 9 remaining · resets 1
In directory since2026-07-052026-07-05
operationalpartialdownno data

LectServe vs Nexmo API: common questions

Which is more reliable, LectServe or Nexmo API?

On our scheduled checks, Nexmo API leads on measured uptime — LectServe at 99.02% versus Nexmo 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, LectServe or Nexmo API?

Nexmo API has the lower median latency in our checks — LectServe responds in 786 ms versus Nexmo API at 567 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 LectServe and Nexmo API need an API key?

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

Can I call LectServe and Nexmo API from the browser?

Neither sends browser-friendly CORS headers reliably, so call LectServe and Nexmo API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are LectServe and Nexmo API free for commercial use?

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