JPL Close Approach vs USPTO
Same instrument, two spec sheets — measured, not claimed.
JPL Close Approach vs USPTO: common questions
Which is more reliable, JPL Close Approach or USPTO?
On our scheduled checks, USPTO leads on measured uptime — JPL Close Approach at —% versus USPTO 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 USPTO need an API key?
Neither needs a paid key — JPL Close Approach is callable with no signup, and USPTO is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call JPL Close Approach and USPTO from the browser?
Neither sends browser-friendly CORS headers reliably, so call JPL Close Approach and USPTO 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 USPTO free for commercial use?
JPL Close Approach has unclear commercial terms, and USPTO 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.