PokéAPI vs xkcd

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial usenono
Data licenseFair-use fan dataCC BY-NC 2.5
Free tierUnlimited (be reasonable)Free, no API key
Rate limitNone — locally cache pleaseUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

PokéAPI vs xkcd: common questions

Which is more reliable, PokéAPI or xkcd?

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

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

Can I call PokéAPI and xkcd from the browser?

Only PokéAPI is browser-friendly — it returns CORS headers over HTTPS. xkcd needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are PokéAPI and xkcd free for commercial use?

PokéAPI is personal/non-commercial only, and xkcd is personal/non-commercial only. 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.