shipapis
StarSubmit an APISubmit API

Numverify vs RandomUser

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

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

Numverify vs RandomUser: common questions

Which is more reliable, Numverify or RandomUser?

Both are neck-and-neck — Numverify and RandomUser each measure 100% 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.

Which is faster, Numverify or RandomUser?

RandomUser has the lower median latency in our checks — Numverify responds in 449 ms versus RandomUser at 210 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 Numverify and RandomUser need an API key?

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

Can I call Numverify and RandomUser from the browser?

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

Are Numverify and RandomUser free for commercial use?

Numverify 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.