Open VSX Registry API vs SnapshotAPI

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

Uptime · 30d
Uptime · 90d100%6.9%
Uptime · 30d100%0.0%
P50 · ms245396
P95 · ms693547
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit10800 req/window · 10799 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open VSX Registry API vs SnapshotAPI: common questions

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

On our scheduled checks, Open VSX Registry API leads on measured uptime — Open VSX Registry API at 100% versus SnapshotAPI at 6.9% 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, Open VSX Registry API or SnapshotAPI?

Open VSX Registry API has the lower median latency in our checks — Open VSX Registry API responds in 245 ms versus SnapshotAPI at 396 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 Open VSX Registry API and SnapshotAPI need an API key?

Open VSX Registry API needs no key, while SnapshotAPI requires a free API key. If you want to start calling without signup, reach for Open VSX Registry API first.

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

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

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

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