Deck of Cards vs Zelda

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms401903
P95 · ms36451380
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Deck of Cards vs Zelda: common questions

Which is more reliable, Deck of Cards or Zelda?

On our scheduled checks, Zelda leads on measured uptime — Deck of Cards at 99.02% versus Zelda 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, Deck of Cards or Zelda?

Deck of Cards has the lower median latency in our checks — Deck of Cards responds in 401 ms versus Zelda at 903 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 Deck of Cards and Zelda need an API key?

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

Can I call Deck of Cards and Zelda from the browser?

Yes — both Deck of Cards and Zelda 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 Deck of Cards and Zelda free for commercial use?

Deck of Cards has unclear commercial terms, and Zelda 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.