Lichess vs Magic: The Gathering

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

Uptime · 30d
Uptime · 90d99.02%98.0%
Uptime · 30d100%96.7%
P50 · ms436394
P95 · ms40883556
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished1000 req/window · 999 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs Magic: The Gathering: common questions

Which is more reliable, Lichess or Magic: The Gathering?

On our scheduled checks, Lichess leads on measured uptime — Lichess at 99.02% versus Magic: The Gathering at 98.0% 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 Magic: The Gathering?

Magic: The Gathering has the lower median latency in our checks — Lichess responds in 436 ms versus Magic: The Gathering at 394 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 Magic: The Gathering need an API key?

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

Can I call Lichess and Magic: The Gathering from the browser?

Yes — both Lichess and Magic: The Gathering send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Lichess and Magic: The Gathering free for commercial use?

Lichess has unclear commercial terms, and Magic: The Gathering 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.