PotterDB vs xkcd
Same instrument, two spec sheets — measured, not claimed.
PotterDB vs xkcd: common questions
Which is more reliable, PotterDB or xkcd?
Both are neck-and-neck — PotterDB and xkcd each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, PotterDB or xkcd?
xkcd has the lower median latency in our checks — PotterDB responds in 525 ms versus xkcd at 164 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do PotterDB and xkcd need an API key?
Neither needs a paid key — PotterDB 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 PotterDB and xkcd from the browser?
Only PotterDB 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 PotterDB and xkcd free for commercial use?
PotterDB 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.