shipapis
StarSubmit an APISubmit API

Bacon Ipsum vs Numverify

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

APIBacon IpsumHEALTHY95NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms359449
P95 · ms13281488
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bacon Ipsum vs Numverify: common questions

Which is more reliable, Bacon Ipsum or Numverify?

On our scheduled checks, Numverify leads on measured uptime — Bacon Ipsum at 99.02% versus Numverify at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Bacon Ipsum or Numverify?

Bacon Ipsum has the lower median latency in our checks — Bacon Ipsum responds in 359 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 Bacon Ipsum and Numverify need an API key?

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

Can I call Bacon Ipsum and Numverify from the browser?

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

Bacon Ipsum 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.