Traveller Map 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

Traveller Map vs PotterDB: common questions

Which is more reliable, Traveller Map or PotterDB?

Only PotterDB is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Traveller Map and PotterDB need an API key?

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

Yes — both Traveller Map 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 Traveller Map and PotterDB free for commercial use?

Traveller Map 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.