shipapis
StarSubmit an APISubmit API

iDigBio vs JPL Close Approach

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

APIiDigBioNEW—JPL Close ApproachNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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

iDigBio vs JPL Close Approach: common questions

Which is more reliable, iDigBio or JPL Close Approach?

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

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

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

Only iDigBio 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 iDigBio and JPL Close Approach free for commercial use?

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