DocForge vs Numverify

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1583449
P95 · ms24851488
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs Numverify: common questions

Which is more reliable, DocForge or Numverify?

Both are neck-and-neck — DocForge and Numverify 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, DocForge or Numverify?

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

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

Can I call DocForge and Numverify from the browser?

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

Are DocForge and Numverify free for commercial use?

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