shipapis
StarSubmit an APISubmit API

Numverify vs Beeceptor

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

APINumverifyUNMONITORED—BeeceptorNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree public echo host, no signup
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Numverify vs Beeceptor: common questions

Which is more reliable, Numverify or Beeceptor?

Only Beeceptor is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Numverify and Beeceptor need an API key?

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

Can I call Numverify and Beeceptor from the browser?

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

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