shipapis
StarSubmit an APISubmit API

Numverify vs UrlBae

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

APINumverifyNEW—UrlBaeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Numverify vs UrlBae: common questions

Which is more reliable, Numverify or UrlBae?

On our scheduled checks, UrlBae leads on measured uptime — Numverify at —% versus UrlBae 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 Numverify and UrlBae need an API key?

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

Neither sends browser-friendly CORS headers reliably, so call Numverify and UrlBae from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Numverify and UrlBae free for commercial use?

Numverify has unclear commercial terms, and UrlBae 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.