shipapis
StarSubmit an APISubmit API

Lanyard vs LectServe

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

APILanyardHEALTHY75LectServeHEALTHY69
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms279786
P95 · ms15881633
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?

Both are neck-and-neck — Lanyard and LectServe each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Lanyard or LectServe?

Lanyard has the lower median latency in our checks — Lanyard responds in 279 ms versus LectServe at 786 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 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.