shipapis
StarSubmit an APISubmit API

Metro Lisboa vs NHTSA

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

APIMetro LisboaHEALTHY82NHTSAHEALTHY87
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms1308760
P95 · ms24594902
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. Government work)
Free tierFree — limits not publishedFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs NHTSA: common questions

Which is more reliable, Metro Lisboa or NHTSA?

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

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

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

Can I call Metro Lisboa and NHTSA from the browser?

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

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