shipapis
StarSubmit an APISubmit API

Metro Lisboa vs ProblemsByVin

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

APIMetro LisboaHEALTHY82ProblemsByVinHEALTHY88
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1308738
P95 · ms24592512
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree — limits not publishedFree (weekly-refreshed static JSON datasets)
Rate limitUnpublishedUnpublished (static JSON files)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs ProblemsByVin: common questions

Which is more reliable, Metro Lisboa or ProblemsByVin?

Both are neck-and-neck — Metro Lisboa and ProblemsByVin 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, Metro Lisboa or ProblemsByVin?

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

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

Can I call Metro Lisboa and ProblemsByVin from the browser?

Only ProblemsByVin 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 ProblemsByVin free for commercial use?

Metro Lisboa has unclear commercial terms, and ProblemsByVin allows commercial use on its free tier. 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.