PotterDB vs XIVAPI

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms525578
P95 · ms11931451
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (data derived from Harry Potter Fandom, CC BY-SA)Unverified; game content © Square Enix
Free tierFree — no keyFree; optional free key raises limits
Rate limitUnpublishedRate-limited; higher limits with a free key (see docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

PotterDB vs XIVAPI: common questions

Which is more reliable, PotterDB or XIVAPI?

Both are neck-and-neck — PotterDB and XIVAPI 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 XIVAPI?

PotterDB has the lower median latency in our checks — PotterDB responds in 525 ms versus XIVAPI at 578 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 XIVAPI need an API key?

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

Can I call PotterDB and XIVAPI from the browser?

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

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