USPTO vs Open Notify

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 licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited (volunteer-run)
Rate limitUnpublishedPlease be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

USPTO vs Open Notify: common questions

Which is more reliable, USPTO or Open Notify?

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

Neither needs a paid key — USPTO is callable with no signup, and Open Notify is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call USPTO and Open Notify from the browser?

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

Are USPTO and Open Notify free for commercial use?

USPTO has unclear commercial terms, and Open Notify 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.