Numverify vs Yes No

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms449692
P95 · ms14881165
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Numverify vs Yes No: common questions

Which is more reliable, Numverify or Yes No?

Both are neck-and-neck — Numverify and Yes No 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 Yes No?

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

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

Can I call Numverify and Yes No from the browser?

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

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