MediaCaption API vs Openwhyd

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

Uptime · 30d
Uptime · 90d100%90.9%
Uptime · 30d100%90.9%
P50 · ms1062239
P95 · ms1062326
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverified
Free tier10 credits when you sign upFree — no key required
Rate limit60 req/min100 req/window · 99 remaining · resets 60
In directory since2026-07-182026-07-05
operationalpartialdownno data

MediaCaption API vs Openwhyd: common questions

Which is more reliable, MediaCaption API or Openwhyd?

On our scheduled checks, MediaCaption API leads on measured uptime — MediaCaption API at 100% versus Openwhyd at 90.9% 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, MediaCaption API or Openwhyd?

Openwhyd has the lower median latency in our checks — MediaCaption API responds in 1062 ms versus Openwhyd at 239 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 MediaCaption API and Openwhyd need an API key?

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

Can I call MediaCaption API and Openwhyd from the browser?

Only MediaCaption API is browser-friendly — it returns CORS headers over HTTPS. Openwhyd needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are MediaCaption API and Openwhyd free for commercial use?

MediaCaption API allows commercial use on its free tier, 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.