shipapis
StarSubmit an APISubmit API

Vector Express v2.0 vs Yes-as-a-Service

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

APIVector Express v2.0NEW—Yes-as-a-ServiceNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFreeFree — limits not published
Rate limit5 req/window · 4 remaining · resets 1783513379Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Vector Express v2.0 vs Yes-as-a-Service: common questions

Which is more reliable, Vector Express v2.0 or Yes-as-a-Service?

On our scheduled checks, Yes-as-a-Service leads on measured uptime — Vector Express v2.0 at —% versus Yes-as-a-Service 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 Vector Express v2.0 and Yes-as-a-Service need an API key?

Neither needs a paid key — Vector Express v2.0 is callable with no signup, and Yes-as-a-Service is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Vector Express v2.0 and Yes-as-a-Service from the browser?

Only Yes-as-a-Service is browser-friendly — it returns CORS headers over HTTPS. Vector Express v2.0 needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Vector Express v2.0 and Yes-as-a-Service free for commercial use?

Vector Express v2.0 has unclear commercial terms, and Yes-as-a-Service 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.