PotterDB vs TCGdex
Same instrument, two spec sheets — measured, not claimed.
PotterDB vs TCGdex: common questions
Which is more reliable, PotterDB or TCGdex?
On our scheduled checks, PotterDB leads on measured uptime — PotterDB at 100% versus TCGdex at 98.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, PotterDB or TCGdex?
TCGdex has the lower median latency in our checks — PotterDB responds in 525 ms versus TCGdex at 161 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 TCGdex need an API key?
Neither needs a paid key — PotterDB is callable with no signup, and TCGdex is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call PotterDB and TCGdex from the browser?
Yes — both PotterDB and TCGdex 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 TCGdex free for commercial use?
PotterDB has unclear commercial terms, and TCGdex 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.