shipapis
StarSubmit an APISubmit API

Lichess vs Yu-Gi-Oh!

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

APILichessHEALTHY74Yu-Gi-Oh!HEALTHY95
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms436267
P95 · ms40883948
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (Konami IP)
Free tierFree — limits not publishedFree, no API key
Rate limitUnpublished20 requests per second per IP (documented)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs Yu-Gi-Oh!: common questions

Which is more reliable, Lichess or Yu-Gi-Oh!?

Both are neck-and-neck — Lichess and Yu-Gi-Oh! each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Lichess or Yu-Gi-Oh!?

Yu-Gi-Oh! has the lower median latency in our checks — Lichess responds in 436 ms versus Yu-Gi-Oh! at 267 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 Yu-Gi-Oh! need an API key?

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

Can I call Lichess and Yu-Gi-Oh! from the browser?

Yes — both Lichess and Yu-Gi-Oh! 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 Yu-Gi-Oh! free for commercial use?

Lichess has unclear commercial terms, and Yu-Gi-Oh! 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.