Not Human Search vs Open Notify

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

Uptime · 30d
Uptime · 90d100%71.6%
Uptime · 30d100%65.0%
P50 · ms239241
P95 · ms9114298
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedn/a
Free tierFree — no key for read endpoints (paid API-key plans offered)Unlimited (volunteer-run)
Rate limitUnpublishedPlease be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

Not Human Search vs Open Notify: common questions

Which is more reliable, Not Human Search or Open Notify?

On our scheduled checks, Not Human Search leads on measured uptime — Not Human Search at 100% versus Open Notify at 71.6% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Not Human Search or Open Notify?

Not Human Search has the lower median latency in our checks — Not Human Search responds in 239 ms versus Open Notify at 241 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Not Human Search and Open Notify need an API key?

Neither needs a paid key — Not Human Search 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 Not Human Search and Open Notify from the browser?

Only Not Human Search is browser-friendly — it returns CORS headers over HTTPS. Open Notify needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Not Human Search and Open Notify free for commercial use?

Not Human Search 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.