shipapis
StarSubmit an APISubmit API

Lanyard vs Public Time API

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

APILanyardHEALTHY78Public Time APIHEALTHY97
Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%98.3%
P50 · ms151311
P95 · ms1588449
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree — limits not published
Rate limitUnpublishedRetry-After: 1020s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs Public Time API: common questions

Which is more reliable, Lanyard or Public Time API?

On our scheduled checks, Lanyard leads on measured uptime — Lanyard at 100% versus Public Time API at 99.44% 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, Lanyard or Public Time API?

Lanyard has the lower median latency in our checks — Lanyard responds in 151 ms versus Public Time API at 311 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 Public Time API need an API key?

Neither needs a paid key — Lanyard 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 Lanyard and Public Time API from the browser?

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

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