shipapis
StarSubmit an APISubmit API

Poof vs Trakt

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

APIPoofDEAD0TraktDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
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

Poof vs Trakt: common questions

Which is more reliable, Poof or Trakt?

Both are neck-and-neck — Poof and Trakt each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do Poof and Trakt need an API key?

Both ask you to authenticate — Poof 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 Poof and Trakt from the browser?

Only Poof 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 Poof and Trakt free for commercial use?

Poof 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.