Lichess vs TCGApi

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs TCGApi: common questions

Which is more reliable, Lichess or TCGApi?

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

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

Can I call Lichess and TCGApi from the browser?

Yes — both Lichess and TCGApi 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 TCGApi free for commercial use?

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