shipapis
StarSubmit an APISubmit API

Replicate vs Open Notify

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

APIReplicateUNMONITORED—Open NotifyDYING—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedn/a
Free tierFree tier — API key requiredUnlimited (volunteer-run)
Rate limitUnpublishedPlease be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

Replicate vs Open Notify: common questions

Which is more reliable, Replicate or Open Notify?

Only Open Notify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Replicate and Open Notify need an API key?

Open Notify needs no key, while Replicate requires a free API key. If you want to start calling without signup, reach for Open Notify first.

Can I call Replicate and Open Notify from the browser?

Neither sends browser-friendly CORS headers reliably, so call Replicate 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 Replicate and Open Notify free for commercial use?

Replicate 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.