Loading…
BetterSuite is built for teams who see on-demand as a business — not a feature.
The Google Maps API cost for taxi apps is between $0.32 and $0.52 per completed ride at Google's October 2026 list prices. If you are comparing quotes for a taxi dispatch platform, it is the line to look for. The lower figure is a lean app, the higher one asks Google for everything, and both count ride requests that never become rides. Before you sign, ask who pays that bill.
A rider drops a pin, types a destination and asks for a price. The system ranks nearby drivers by arrival time. A driver navigates to the pickup and then the drop-off, while the rider watches the arrival time update. Each step is one or more billable calls.
The table prices each call at Google's list price, which is what you pay once the free allowance runs out. The prices are Google's published Maps API pricing, read on 4 October 2026. Accounts billed in India have a separate, lower list.
| Step | Google product | Calls | Cost |
|---|---|---|---|
| Pickup pin to address | Geocoding | 2 | $0.010 |
| Destination search | Autocomplete, 8 keystrokes, plus Place Details | 9 | $0.028 |
| Fare quote | Routes API, traffic-aware | 1 | $0.010 |
| Finding the nearest drivers | Route Matrix, traffic-aware, 10 drivers | 10 | $0.100 |
| Driver to pickup, then to drop-off | Routes API, traffic-aware | 2 | $0.020 |
| Turn-by-turn for the driver | Navigation SDK, 2 destinations | 2 | $0.050 |
| Arrival-time updates, one a minute for 20 minutes | Routes API, traffic-aware | 20 | $0.200 |
| One completed ride | 46 | $0.42 |
The call counts are our assumptions for an ordinary city trip in a taxi or ride-hailing app, not a measurement of any one. To fit them to yours: about $0.12 is fixed, and each driver checked and each arrival-time refresh adds a cent.
That is the bill for an app that asks Google for everything. Arrival-time updates are almost half of it, by choice. An app that works out the arrival time from the route it already holds skips the last row. That lean build costs about $0.22 a ride.
Not every ride request becomes a ride. A rider checks the price and closes the app, or no driver accepts. Google bills each call as it is made, so you pay for those too.
We count a failed request at the first four rows of the table, about $0.15. A price check that goes no further costs about $0.05, and a cancellation at the kerb costs more. If 60% of ride requests end as completed rides, there are two failed requests for every three rides. Spread across those rides, that adds about $0.10 each: $0.52 per completed ride for the full build and $0.32 for the lean one.
Check the completion rate in your own data. At 50% the full build is $0.57, and at 70% it is $0.48.
List price is the ceiling. Google gives every billable item a free monthly allowance, and unit prices fall with volume. Applied to the same call counts:
| Completed rides a month | Full build | Lean build |
|---|---|---|
| 200 | $0 | $0 |
| 500 | $100, or $0.20 a ride | $33, or $0.07 a ride |
| 1,000 | $340, or $0.34 a ride | $150, or $0.15 a ride |
| 5,000 | $2,300, or $0.46 a ride | $1,340, or $0.27 a ride |
| 20,000 | $8,800, or $0.44 a ride | $5,500, or $0.28 a ride |
Put your own numbers in:
Google Maps Platform list prices, free monthly allowances and volume bands as published on 4 October 2026.
The free tier covers roughly the first 200 rides a month. By a few thousand rides you are close to list price, and volume discounts are still far off: Routes API pricing drops by a fifth only past 100,000 traffic-aware calls a month.
Google sells two other arrangements. One is a set of fixed monthly bundles; the largest, $1,200 for 250,000 calls, works out to about $0.33 a ride on the full build. The other is its Mobility services, sold under a signed contract and billed per completed trip, at prices Google does not publish.
The bill is the same whether the fare is $2 or $20, so it weighs most on short rides.
| Fare | Lean build, $0.32 | Full build, $0.52 |
|---|---|---|
| $2 | 16% | 26% |
| $5 | 6.4% | 10.4% |
| $10 | 3.2% | 5.2% |
| $20 | 1.6% | 2.6% |
You do not keep the fare. If your commission is 20%, your take on a $5 ride is $1.00, and the full build's maps bill is half of it.
By its own account of how it predicts traffic, its traffic picture comes from the location data of people navigating with Google Maps, which makes its arrival times hard to match. In 2025 Germany's competition authority called Google Maps Platform "by far the most important provider" of map services to businesses. It named HERE, Mapbox and TomTom among the other providers.
A cheaper provider lowers the price of each call. It does not change who pays, or that the bill grows with every ride. So many platforms for ride-hailing software call Google for everything and pass the bill on to you.
A platform can handle maps in three ways.
Add four questions to our checklist for choosing taxi dispatch software:
If the bill is already yours, two settings move it most: how many drivers the system checks for each ride request, and how it refreshes arrival times. Ask your vendor what both are set to, and put a quota and a budget alert on the key in Google Cloud.
Our fee on a completed ride is 1.9% of the fare, on top of a flat monthly subscription. That is the rate in October 2026, and our pricing page has the current one. On any fare under about $27, the full build's maps bill is larger than that transaction fee. Paying Google for every ride does not work at that price, so we run our own geo engine and keep Google as the backup.
The engine runs on OpenStreetMap road data. It learns typical speeds for each road and time of week from the trips your own drivers have driven, and from historical traffic data.
In every region you operate in, it compares its arrival times with Google's. Once the two agree within 5%, our engine serves that region and Google stays as the backup. Today our engine answers most routing and address-search calls on the platform. Google still answers where ours is not good enough yet: a region below that bar, or an address our data cannot resolve.
Our own answers to the four questions, on the cloud plan: you supply no Google Maps key, and the calls land on our account. The provider is our engine, with Google behind it. Arrival times during a trip come from the route we already hold, so a re-route is the only map call a trip adds. No plan has a maps quota or surcharge, so your maps cost stays at zero when volume doubles. If you host BetterSuite yourself, the map provider is yours to choose and pay for.
Running our own engine also changed what we could include. Re-routing a driver who leaves the route is a new route request every time, and at a price per call you ration it. On our engine we do not have to. Turn-by-turn navigation inside the driver app, in 18 languages, comes with the on-demand platform as well.
Between $0.32 and $0.52 per completed ride at Google's list prices. The lower figure is an app that works out arrival times itself, and the higher one asks Google every minute. Both include about $0.10 for ride requests that never become rides, at a 60% completion rate.
Partly. Since March 2025 each billable item has a free monthly allowance of 10,000, 5,000 or 1,000 calls, in place of the old $200 credit.
Uber's 2019 filing for its stock-market listing says it paid Google about $58 million over three years, from 2016 to 2018. Uber negotiates its own contract. You start at list price.
The data can be free. OpenStreetMap is open data, and open-source engines such as Valhalla and OSRM route on it. The work is not free: someone has to host the engine, keep the map current and prove its arrival times are accurate.
Ask your current provider who pays for maps, then see what BetterSuite charges per completed ride.
