shipapis
StarSubmit an APISubmit API

Open VSX Registry API vs Shields

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

APIOpen VSX Registry APINEW—ShieldsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit10800 req/window · 10799 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open VSX Registry API vs Shields: common questions

Which is more reliable, Open VSX Registry API or Shields?

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

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

Can I call Open VSX Registry API and Shields from the browser?

Yes — both Open VSX Registry API and Shields send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Open VSX Registry API and Shields free for commercial use?

Open VSX Registry API has unclear commercial terms, and Shields 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.