BVG transport.rest vs CarAPI

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

Uptime · 30d
Uptime · 90d71.6%100%
Uptime · 30d66.7%100%
P50 · ms11061223
P95 · ms44312287
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BVG transport.rest vs CarAPI: common questions

Which is more reliable, BVG transport.rest or CarAPI?

On our scheduled checks, CarAPI leads on measured uptime — BVG transport.rest at 71.6% versus CarAPI 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, BVG transport.rest or CarAPI?

BVG transport.rest has the lower median latency in our checks — BVG transport.rest responds in 1106 ms versus CarAPI at 1223 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 BVG transport.rest and CarAPI need an API key?

BVG transport.rest needs no key, while CarAPI requires a free API key. If you want to start calling without signup, reach for BVG transport.rest first.

Can I call BVG transport.rest and CarAPI from the browser?

Only BVG transport.rest is browser-friendly — it returns CORS headers over HTTPS. CarAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BVG transport.rest and CarAPI free for commercial use?

BVG transport.rest has unclear commercial terms, and CarAPI 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.