shipapis
StarSubmit an APISubmit API

JPL Close Approach vs OpenAlex

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

APIJPL Close ApproachNEW—OpenAlexNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC0
Free tierFree — limits not publishedFree tier (~$1/day of usage); free API key available for more
Rate limitUnpublishedUsage-metered free tier (~$1/day per docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

JPL Close Approach vs OpenAlex: common questions

Which is more reliable, JPL Close Approach or OpenAlex?

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

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

Can I call JPL Close Approach and OpenAlex from the browser?

Only OpenAlex is browser-friendly — it returns CORS headers over HTTPS. JPL Close Approach needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are JPL Close Approach and OpenAlex free for commercial use?

JPL Close Approach has unclear commercial terms, and OpenAlex allows commercial use on its free tier. 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.