shipapis
StarSubmit an APISubmit API

Kroki vs Numverify

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

APIKrokiNEW—NumverifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
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

Kroki vs Numverify: common questions

Which is more reliable, Kroki or Numverify?

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

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

Can I call Kroki and Numverify from the browser?

Only Kroki 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 Kroki and Numverify free for commercial use?

Kroki 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.