How? It starts with open APIs. Some cities require open APIs, and some operators provide open APIs willingly. They let anyone get real-time data about bikes, scooters, and cars. At Transit, we use that data to see how nearby 🚲🛴🚘 vehicles can be combined with nearby transit for the fastest possible trip. (With closed APIs? Much harder to do.)

Then we leverage recent improvements, like offline trip planning — which makes it faster to calculate the best transit transfer —plus new, elevation-sensitive trip plans, which ensure you don’t get sent up mountains like a pedal-pushing Sisyphus.

As a final flourish: we let you pay for and unlock vehicles, right from our app. We’ve baked these features into our trip planner in 10 cities (including Chicago, Toronto, Montreal, Detroit, Minneapolis…) with help from our partners, so you can start your trip in one tap.

After all: showing faster trips is only half the battle — you have to encourage people to actually take the trips being suggested. (Ain’t nobody gonna download five extra apps to save five minutes.) But by elegantly unifying the planning, paying, and unlocking experience, your multimodal time gains get more tangible. ⌛️👉⏳

We love public transit. We love bikes. We love scooters. But when they work in concert, you end up with something even better than the sum of their parts. Multimodal trips shouldn’t require juggling apps (or local expertise) to plan. And now, they don’t. Thanks to open APIs and crafty engineering, we’ve made them accessible to everyone — showing you trips that can legitimately outgun cars.

So, what if the future isn’t teaching four wheels how to drive themselves?

What if it’s just teaching different wheels to drive together?