shipapis
StarSubmit an APISubmit API

TensorFeed vs Open Notify

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

APITensorFeedNEW—Open NotifyDYING—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedn/a
Free tierFree — no key (static JSON feed endpoints)Unlimited (volunteer-run)
Rate limit120 req/window · 119 remaining · resets 60Please be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

TensorFeed vs Open Notify: common questions

Which is more reliable, TensorFeed or Open Notify?

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

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

Can I call TensorFeed and Open Notify 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 TensorFeed and Open Notify free for commercial use?

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