OpenVan vs StayingAPI

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms645143
P95 · ms3603913
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — no auth
Rate limit120 req/window · 119 remaining
In directory since2026-07-052026-09-21
operationalpartialdownno data

OpenVan vs StayingAPI: common questions

Which is more reliable, OpenVan or StayingAPI?

Both are neck-and-neck — OpenVan and StayingAPI 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, OpenVan or StayingAPI?

StayingAPI has the lower median latency in our checks — OpenVan responds in 645 ms versus StayingAPI at 143 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 OpenVan and StayingAPI need an API key?

OpenVan needs no key, while StayingAPI requires a free API key. If you want to start calling without signup, reach for OpenVan first.

Can I call OpenVan and StayingAPI from the browser?

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

Are OpenVan and StayingAPI free for commercial use?

OpenVan has unclear commercial terms, and StayingAPI 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.