CVEDB vs Jumpseller API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CVEDB vs Jumpseller API: common questions

Which is more reliable, CVEDB or Jumpseller API?

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

Neither needs a paid key — CVEDB is callable with no signup, and Jumpseller API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call CVEDB and Jumpseller API from the browser?

Only Jumpseller API is browser-friendly — it returns CORS headers over HTTPS. CVEDB needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are CVEDB and Jumpseller API free for commercial use?

CVEDB has unclear commercial terms, and Jumpseller API 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.