Apimetro vs Metro Lisboa

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms6491308
P95 · ms28692459
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apimetro vs Metro Lisboa: common questions

Which is more reliable, Apimetro or Metro Lisboa?

On our scheduled checks, Metro Lisboa leads on measured uptime — Apimetro at 99.02% versus Metro Lisboa 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, Apimetro or Metro Lisboa?

Apimetro has the lower median latency in our checks — Apimetro responds in 649 ms versus Metro Lisboa at 1308 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 Apimetro and Metro Lisboa need an API key?

Neither needs a paid key — Apimetro is callable with no signup, and Metro Lisboa is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Apimetro and Metro Lisboa from the browser?

Only Apimetro 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 Apimetro and Metro Lisboa free for commercial use?

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