IMDbOT vs ThronesApi

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

Uptime · 30d
Uptime · 90d25.5%97.1%
Uptime · 30d0.0%95.0%
P50 · ms1208890
P95 · ms17394593
Authnonenone
CORSnoyes
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

IMDbOT vs ThronesApi: common questions

Which is more reliable, IMDbOT or ThronesApi?

On our scheduled checks, ThronesApi leads on measured uptime — IMDbOT at 25.5% versus ThronesApi at 97.1% 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, IMDbOT or ThronesApi?

ThronesApi has the lower median latency in our checks — IMDbOT responds in 1208 ms versus ThronesApi at 890 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 IMDbOT and ThronesApi need an API key?

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

Can I call IMDbOT and ThronesApi from the browser?

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

Are IMDbOT and ThronesApi free for commercial use?

IMDbOT has unclear commercial terms, and ThronesApi 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.