Lichess vs Wynncraft

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms436778
P95 · ms40882871
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs Wynncraft: common questions

Which is more reliable, Lichess or Wynncraft?

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

Lichess has the lower median latency in our checks — Lichess responds in 436 ms versus Wynncraft at 778 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 Lichess and Wynncraft need an API key?

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

Can I call Lichess and Wynncraft from the browser?

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

Are Lichess and Wynncraft free for commercial use?

Lichess has unclear commercial terms, and Wynncraft 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.