shipapis
StarSubmit an APISubmit API

Open Notify vs TensorFeed

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

APIOpen NotifyDYING—TensorFeedNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licensen/aUnverified
Free tierUnlimited (volunteer-run)Free — no key (static JSON feed endpoints)
Rate limitPlease be gentle120 req/window · 119 remaining · resets 60
In directory since2026-05-022026-07-05
operationalpartialdownno data

Open Notify vs TensorFeed: common questions

Which is more reliable, Open Notify or TensorFeed?

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

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

Can I call Open Notify and TensorFeed from the browser?

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

Are Open Notify and TensorFeed free for commercial use?

Open Notify has unclear commercial terms, and TensorFeed 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.