shipapis
StarSubmit an APISubmit API

Lichess vs Pokefact API

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

APILichessNEW—Pokefact APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs Pokefact API: common questions

Which is more reliable, Lichess or Pokefact API?

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

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

Can I call Lichess and Pokefact API from the browser?

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

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