Apimetro vs BVG transport.rest

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

Uptime · 30d
Uptime · 90d99.02%71.6%
Uptime · 30d98.3%66.7%
P50 · ms6491106
P95 · ms28694431
Authnonenone
CORSyesyes
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 BVG transport.rest: common questions

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

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

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

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

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

Yes — both Apimetro and BVG transport.rest send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

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

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