Numverify vs PageBolt

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms292279
P95 · ms14881314
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 PageBolt: common questions

Which is more reliable, Numverify or PageBolt?

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

PageBolt has the lower median latency in our checks — Numverify responds in 292 ms versus PageBolt at 279 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 PageBolt need an API key?

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

Neither sends browser-friendly CORS headers reliably, so call Numverify and PageBolt 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 PageBolt free for commercial use?

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