shipapis
StarSubmit an APISubmit API

NeoWs - (Near Earth Object Web Service) vs TasteDive

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

APINeoWs - (Near Earth Object Web Service)NEW—TasteDiveNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitSee documentationUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NeoWs - (Near Earth Object Web Service) vs TasteDive: common questions

Which is more reliable, NeoWs - (Near Earth Object Web Service) or TasteDive?

On our scheduled checks, TasteDive leads on measured uptime — NeoWs - (Near Earth Object Web Service) at —% versus TasteDive 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 NeoWs - (Near Earth Object Web Service) and TasteDive need an API key?

NeoWs - (Near Earth Object Web Service) needs no key, while TasteDive requires a free API key. If you want to start calling without signup, reach for NeoWs - (Near Earth Object Web Service) first.

Can I call NeoWs - (Near Earth Object Web Service) and TasteDive from the browser?

Neither sends browser-friendly CORS headers reliably, so call NeoWs - (Near Earth Object Web Service) and TasteDive from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are NeoWs - (Near Earth Object Web Service) and TasteDive free for commercial use?

NeoWs - (Near Earth Object Web Service) has unclear commercial terms, and TasteDive 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.