shipapis
StarSubmit an APISubmit API

Transport for Philadelphia, US vs BC Ferries

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

APITransport for Philadelphia, USNEW—BC FerriesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for Philadelphia, US vs BC Ferries: common questions

Which is more reliable, Transport for Philadelphia, US or BC Ferries?

On our scheduled checks, BC Ferries leads on measured uptime — Transport for Philadelphia, US 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 Philadelphia, US and BC Ferries need an API key?

Neither needs a paid key — Transport for Philadelphia, US 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 Philadelphia, US and BC Ferries from the browser?

Only BC Ferries is browser-friendly — it returns CORS headers over HTTPS. Transport for Philadelphia, US needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Transport for Philadelphia, US and BC Ferries free for commercial use?

Transport for Philadelphia, US 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.