Findwork vs Lanyard

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms481279
P95 · ms19151588
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — no key; user must be tracked by the Lanyard Discord bot
Rate limit4294967295 req/window · 4294967295 remaining · resets 0Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Findwork vs Lanyard: common questions

Which is more reliable, Findwork or Lanyard?

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

Lanyard has the lower median latency in our checks — Findwork responds in 481 ms versus Lanyard at 279 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 Findwork and Lanyard need an API key?

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

Can I call Findwork and Lanyard from the browser?

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

Are Findwork and Lanyard free for commercial use?

Findwork has unclear commercial terms, and Lanyard 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.