shipapis
StarSubmit an APISubmit API

JPL Close Approach vs Open Science Framework

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

APIJPL Close ApproachNEW—Open Science FrameworkNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

JPL Close Approach vs Open Science Framework: common questions

Which is more reliable, JPL Close Approach or Open Science Framework?

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

Neither needs a paid key — JPL Close Approach is callable with no signup, and Open Science Framework is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call JPL Close Approach and Open Science Framework from the browser?

Neither sends browser-friendly CORS headers reliably, so call JPL Close Approach and Open Science Framework from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are JPL Close Approach and Open Science Framework free for commercial use?

JPL Close Approach has unclear commercial terms, and Open Science Framework 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.