Nebulum Mars Rovers API vs Openwhyd

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

Uptime · 30d
Uptime · 90d92.8%97.2%
Uptime · 30d78.3%100%
P50 · ms454137
P95 · ms14171350
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nebulum Mars Rovers API vs Openwhyd: common questions

Which is more reliable, Nebulum Mars Rovers API or Openwhyd?

On our scheduled checks, Openwhyd leads on measured uptime — Nebulum Mars Rovers API at 92.8% versus Openwhyd at 97.2% 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, Nebulum Mars Rovers API or Openwhyd?

Openwhyd has the lower median latency in our checks — Nebulum Mars Rovers API responds in 454 ms versus Openwhyd at 137 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 Nebulum Mars Rovers API and Openwhyd need an API key?

Neither needs a paid key — Nebulum Mars Rovers API is callable with no signup, and Openwhyd is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Nebulum Mars Rovers API and Openwhyd from the browser?

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

Are Nebulum Mars Rovers API and Openwhyd free for commercial use?

Nebulum Mars Rovers API has unclear commercial terms, and Openwhyd 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.