GraphHopper vs StayingAPI

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

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—143
P95 · ms—913
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-07-052026-09-21
operationalpartialdownno data

GraphHopper vs StayingAPI: common questions

Which is more reliable, GraphHopper or StayingAPI?

On our scheduled checks, StayingAPI leads on measured uptime — GraphHopper at 0.0% versus StayingAPI at 100% 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 GraphHopper and StayingAPI need an API key?

Both ask you to authenticate — GraphHopper uses an API key and StayingAPI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call GraphHopper and StayingAPI from the browser?

Only GraphHopper 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 GraphHopper and StayingAPI free for commercial use?

GraphHopper 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.