shipapis
StarSubmit an APISubmit API

Lanyard vs LectServe

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

APILanyardNEW—LectServeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs LectServe: common questions

Which is more reliable, Lanyard or LectServe?

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

Neither needs a paid key — Lanyard is callable with no signup, and LectServe is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Lanyard and LectServe from the browser?

Only Lanyard 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 Lanyard and LectServe free for commercial use?

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