shipapis
StarSubmit an APISubmit API

Sirv vs Trakt

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

APISirvNEW—TraktREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedTrakt terms — user-contributed data
Free tierFree tier — API key requiredFree OAuth application
Rate limitUnpublished1,000 req every 5 min documented
In directory since2026-07-052026-07-05
operationalpartialdownno data

Sirv vs Trakt: common questions

Which is more reliable, Sirv or Trakt?

On our scheduled checks, Trakt leads on measured uptime — Sirv at —% versus Trakt 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 Sirv and Trakt need an API key?

Both ask you to authenticate — Sirv uses an API key and Trakt uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Sirv and Trakt from the browser?

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

Are Sirv and Trakt free for commercial use?

Sirv has unclear commercial terms, and Trakt 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.