Browshot vs RandomUser

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (generated data; sample photos governed by UI Faces terms)
Free tierFree tier — API key requiredFree — no key or signup
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Browshot vs RandomUser: common questions

Which is more reliable, Browshot or RandomUser?

On our scheduled checks, RandomUser leads on measured uptime — Browshot at —% versus RandomUser at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Browshot and RandomUser need an API key?

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

Can I call Browshot and RandomUser from the browser?

Only RandomUser 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 RandomUser free for commercial use?

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