Numverify vs WakaTime

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms449969
P95 · ms14882993
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree public endpoints; personal data needs API key/OAuth
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Numverify vs WakaTime: common questions

Which is more reliable, Numverify or WakaTime?

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

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

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

Can I call Numverify and WakaTime from the browser?

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

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