Pokefact 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 useunclearno
Data licenseUnverifiedCC BY-NC 2.5
Free tierFree — limits not publishedFree, no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Pokefact API vs xkcd: common questions

Which is more reliable, Pokefact API or xkcd?

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

Neither needs a paid key — Pokefact 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 Pokefact API and xkcd from the browser?

Only Pokefact 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 Pokefact API and xkcd free for commercial use?

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