Deck of Cards vs PotterDB

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 (data derived from Harry Potter Fandom, CC BY-SA)
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Deck of Cards vs PotterDB: common questions

Which is more reliable, Deck of Cards or PotterDB?

On our scheduled checks, PotterDB leads on measured uptime — Deck of Cards at —% versus PotterDB 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 Deck of Cards and PotterDB need an API key?

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

Can I call Deck of Cards and PotterDB from the browser?

Yes — both Deck of Cards and PotterDB 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 Deck of Cards and PotterDB free for commercial use?

Deck of Cards has unclear commercial terms, and PotterDB 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.