PokéAPI 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 usenounclear
Data licenseFair-use fan dataUnverified (data derived from Harry Potter Fandom, CC BY-SA)
Free tierUnlimited (be reasonable)Free — no key
Rate limitNone — locally cache pleaseUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

PokéAPI vs PotterDB: common questions

Which is more reliable, PokéAPI or PotterDB?

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

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

Yes — both PokéAPI 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 PokéAPI and PotterDB free for commercial use?

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