shipapis
StarSubmit an APISubmit API

Transport for United States vs BC Ferries

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

APITransport for United StatesNEW—BC FerriesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseData copyright transit agencies / Umo IQUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for United States vs BC Ferries: common questions

Which is more reliable, Transport for United States or BC Ferries?

On our scheduled checks, BC Ferries leads on measured uptime — Transport for United States at —% versus BC Ferries at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Transport for United States and BC Ferries need an API key?

Neither needs a paid key — Transport for United States is callable with no signup, and BC Ferries is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Transport for United States and BC Ferries from the browser?

Yes — both Transport for United States and BC Ferries 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 Transport for United States and BC Ferries free for commercial use?

Transport for United States has unclear commercial terms, and BC Ferries 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.