shipapis
StarSubmit an APISubmit API

Browshot vs Rendex

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

APIBrowshotDEAD0RendexDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Browshot vs Rendex: common questions

Which is more reliable, Browshot or Rendex?

Both are neck-and-neck — Browshot and Rendex each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do Browshot and Rendex need an API key?

Both ask you to authenticate — Browshot uses an API key and Rendex 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 Browshot and Rendex from the browser?

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

Are Browshot and Rendex free for commercial use?

Browshot has unclear commercial terms, and Rendex 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.