Affirmations.dev 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
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedSee documentation
In directory since2026-07-052026-07-05
operationalpartialdownno data

Affirmations.dev vs NeoWs - (Near Earth Object Web Service): common questions

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

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

Neither needs a paid key — Affirmations.dev 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 Affirmations.dev and NeoWs - (Near Earth Object Web Service) from the browser?

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

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

Affirmations.dev has unclear commercial terms, 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.