Scryfall vs TETR.IO

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

Uptime · 30d
Uptime · 90d94.2%100%
Uptime · 30d95.0%100%
P50 · ms470337
P95 · ms2767906
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCard data free to use; MTG content © Wizards of the Coast (see docs)Unverified
Free tierFree, no API key requiredFree, no API key
Rate limit~10 requests/second; docs ask for 50-100 ms between requestsHonor server-provided cache expiry (~60s); docs require caching
In directory since2026-07-052026-07-05
operationalpartialdownno data

Scryfall vs TETR.IO: common questions

Which is more reliable, Scryfall or TETR.IO?

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

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

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

Can I call Scryfall and TETR.IO from the browser?

Only TETR.IO is browser-friendly — it returns CORS headers over HTTPS. Scryfall needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Scryfall and TETR.IO free for commercial use?

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