MediaCaption API vs Wallhaven

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

Uptime · 30d
Uptime · 90d100%84.2%
Uptime · 30d100%71.7%
P50 · ms1277404
P95 · ms21013981
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverified
Free tier10 credits when you sign upFree tier — key may be required
Rate limit60 req/min45 req/window · 44 remaining
In directory since2026-07-182026-07-05
operationalpartialdownno data

MediaCaption API vs Wallhaven: common questions

Which is more reliable, MediaCaption API or Wallhaven?

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

Wallhaven has the lower median latency in our checks — MediaCaption API responds in 1277 ms versus Wallhaven at 404 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 Wallhaven need an API key?

Both ask you to authenticate — MediaCaption API uses an API key and Wallhaven uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call MediaCaption API and Wallhaven from the browser?

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

Are MediaCaption API and Wallhaven free for commercial use?

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