Metro Lisboa vs Sabre for Developers

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

Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d100%100%
P50 · ms710299
P95 · ms24591603
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs Sabre for Developers: common questions

Which is more reliable, Metro Lisboa or Sabre for Developers?

On our scheduled checks, Sabre for Developers leads on measured uptime — Metro Lisboa at 99.44% versus Sabre for Developers 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.

Which is faster, Metro Lisboa or Sabre for Developers?

Sabre for Developers has the lower median latency in our checks — Metro Lisboa responds in 710 ms versus Sabre for Developers at 299 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 Metro Lisboa and Sabre for Developers need an API key?

Metro Lisboa needs no key, while Sabre for Developers requires a free API key. If you want to start calling without signup, reach for Metro Lisboa first.

Can I call Metro Lisboa and Sabre for Developers from the browser?

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

Are Metro Lisboa and Sabre for Developers free for commercial use?

Metro Lisboa has unclear commercial terms, and Sabre for Developers 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.