shipapis
StarSubmit an APISubmit API

Battle.net vs Lichess

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

APIBattle.netNEW—LichessNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Lichess: common questions

Which is more reliable, Battle.net or Lichess?

On our scheduled checks, Lichess leads on measured uptime — Battle.net at —% versus Lichess 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 Battle.net and Lichess need an API key?

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

Can I call Battle.net and Lichess from the browser?

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

Are Battle.net and Lichess free for commercial use?

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