shipapis
StarSubmit an APISubmit API

Apify vs Open VSX Registry API

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

APIApifyHEALTHY96Open VSX Registry APIHEALTHY95
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms381245
P95 · ms765693
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished10800 req/window · 10799 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apify vs Open VSX Registry API: common questions

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

Both are neck-and-neck — Apify and Open VSX Registry API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Apify or Open VSX Registry API?

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

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

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

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

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

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