shipapis
StarSubmit an APISubmit API

Lichess vs Steam

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

APILichessNEW—SteamNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no API key
Rate limitUnpublishedUnpublished (undocumented endpoint; IP rate-limited)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs Steam: common questions

Which is more reliable, Lichess or Steam?

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

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

Can I call Lichess and Steam from the browser?

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

Are Lichess and Steam free for commercial use?

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