An API of Ice And Fire vs Trakt

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

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

An API of Ice And Fire vs Trakt: common questions

Which is more reliable, An API of Ice And Fire or Trakt?

On our scheduled checks, Trakt leads on measured uptime — An API of Ice And Fire 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 An API of Ice And Fire and Trakt need an API key?

An API of Ice And Fire needs no key, while Trakt requires a free API key. If you want to start calling without signup, reach for An API of Ice And Fire first.

Can I call An API of Ice And Fire and Trakt from the browser?

Only An API of Ice And Fire 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 An API of Ice And Fire and Trakt free for commercial use?

An API of Ice And Fire 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.