Lichess vs XIVAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified; game content © Square Enix
Free tierFree — limits not publishedFree; optional free key raises limits
Rate limitUnpublishedRate-limited; higher limits with a free key (see docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lichess vs XIVAPI: common questions

Which is more reliable, Lichess or XIVAPI?

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

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

Can I call Lichess and XIVAPI from the browser?

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

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