shipapis
StarSubmit an APISubmit API

TETR.IO vs Zelda

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

APITETR.IONEW—ZeldaNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API keyFree — limits not published
Rate limitHonor server-provided cache expiry (~60s); docs require cachingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

TETR.IO vs Zelda: common questions

Which is more reliable, TETR.IO or Zelda?

On our scheduled checks, Zelda leads on measured uptime — TETR.IO at —% versus Zelda at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do TETR.IO and Zelda need an API key?

Neither needs a paid key — TETR.IO 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 TETR.IO and Zelda from the browser?

Yes — both TETR.IO 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 TETR.IO and Zelda free for commercial use?

TETR.IO 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.