Raider vs Scryfall

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

Uptime · 30d
Uptime · 90d100%96.1%
Uptime · 30d100%98.3%
P50 · ms223470
P95 · ms12222767
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (Blizzard game data)Card data free to use; MTG content © Wizards of the Coast (see docs)
Free tierFree, no API key for public dataFree, no API key required
Rate limitUnpublished~10 requests/second; docs ask for 50-100 ms between requests
In directory since2026-07-052026-07-05
operationalpartialdownno data

Raider vs Scryfall: common questions

Which is more reliable, Raider or Scryfall?

On our scheduled checks, Raider leads on measured uptime — Raider at 100% versus Scryfall at 96.1% 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, Raider or Scryfall?

Raider has the lower median latency in our checks — Raider responds in 223 ms versus Scryfall at 470 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 Raider and Scryfall need an API key?

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

Can I call Raider and Scryfall from the browser?

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

Raider has unclear commercial terms, and Scryfall 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.