Agify vs NeoWs - (Near Earth Object Web Service)

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useyesunclear
Data licenseProprietaryUnverified
Free tier100 names/day, no signupFree — limits not published
Rate limit100/day per IPSee documentation
In directory since2026-05-022026-07-05
operationalpartialdownno data

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

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

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

Neither needs a paid key — Agify is callable with no signup, and NeoWs - (Near Earth Object Web Service) is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

Only Agify is browser-friendly — it returns CORS headers over HTTPS. NeoWs - (Near Earth Object Web Service) needs a server-side call or proxy, so factor that into which one fits a front-end project.

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

Agify allows commercial use on its free tier, and NeoWs - (Near Earth Object Web Service) 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.