Introduction
The lowest advertised rate rarely produces the lowest bill. Google meters SKU events, Mapbox meters loads, users, requests and trips, HERE meters transactions, and NextBillion.ai prices by order, asset or API call. The same "route" can be counted four different ways.
This guide compares Google Maps Platform, Mapbox, HERE and NextBillion.ai for US teams, in USD. It covers billing units, free usage, API rates, enterprise terms and the hidden costs that change a monthly total. Where a provider doesn't publish a US dollar rate, that gap is flagged instead of estimated. Confirm every figure on the provider's pricing page before you commit.
Key Takeaways
- Google, Mapbox and HERE bill by usage; NextBillion.ai quotes by order, asset or call.
- Published USD tiers cover Google and Mapbox; HERE and NextBillion.ai rates need a quote.
- Model your own monthly workload instead of comparing one API rate.
- Support, storage rules and matrix limits can move the total.
- Verify all figures against current official pricing pages.
How Maps API Pricing Works
What counts as a billable unit?
Providers count different things:
- Map load: Google JavaScript loads trigger Dynamic Maps; Mapbox counts GL JS map initialization.
- Request: Google Compute Routes bills per query; Mapbox counts a multi-waypoint Directions request as one.
- Element: origins × destinations, billed by Google Route Matrix and Mapbox Matrix.
- Session: Mapbox Search Box groups suggest and retrieve calls under one token.
- MAU or trip: Mapbox Navigation SDK bills monthly active users and trips.
- Transaction: HERE's product-specific unit.
- Order, asset, API call: NextBillion.ai's units. An order is a unique delivery or task within 24 hours, and re-optimizing inside that window still counts as one order.
Retries and polling matter. Google classifies ZERO_RESULTS, DATA_NOT_AVAILABLE and NOT_FOUND responses as billable, so check Google's pricing docs for any free-retry terms on your SKU rather than assuming failed calls are free. Autocomplete is subtle too: a Google session ends when a Place Details request uses the session token, and abandoned sessions fall back to per-request pricing.
Why a published rate is not the total cost
Free allowances, volume bands, support plans, storage rules and contracts all change the final number. Even "geocoding" differs by vendor: Google's Geocoding API allows 3,000 queries per minute, while Mapbox defaults to 1,000 requests per minute.
How to compare fairly
Line up the same capabilities for each vendor: map display, geocoding, autocomplete, directions, matrices, navigation, traffic, optimization, support and deployment. Record the date you checked each price and link the official page.
Google Maps Platform Pricing
The overall model
Google bills per SKU, grouped as Essentials, Pro and Enterprise. Usage aggregates across projects on a billing account, and billing credentials are required for Geocoding, Geolocation and Routes. Free usage is a per-SKU monthly cap, set by the March 2025 changes.
Google also sells subscriptions:
- Starter: $100 for 50,000 calls
- Essentials: $275 for 100,000 calls
- Pro: $1,200 for 250,000 calls
Public list prices per 1,000 events:
| SKU | Free/month | Up to 100k | 100,001-500k | 500,001-1M |
|---|---|---|---|---|
| Dynamic Maps | 10,000 | $7 | $5.60 | $4.20 |
| Static Maps | 10,000 | $2 | $1.60 | $1.20 |
| Geocoding | 10,000 | $5 | $4 | $3 |
| Geolocation | 10,000 | $5 | $4 | $3 |
| Compute Routes Essentials | 10,000 | $5 | $4 | $3 |
| Compute Routes Pro | 5,000 | $10 | $8 | $6 |
| Compute Routes Enterprise | 1,000 | $15 | $12 | $9 |
| Route Matrix Essentials | 10,000 | $5 | $4 | $3 |
The Maps SDK, Embed API and Autocomplete session usage are no-charge SKUs, though related paid calls still bill.
Geocoding and Geolocation
Geocoding converts addresses to coordinates and back. Forward and reverse share one SKU at $5 per 1,000 after 10,000 free requests.
Geolocation is different. It turns cell-tower, Wi-Fi and device data into coordinates and an accuracy radius, not an address. It uses the same $5 rate and 10,000 free requests.
Neither is unlimited. Caching rules also apply: Geocoding and Routes latitude/longitude can be cached for 30 days, and Geocoding content cannot be shown on a non-Google map.
Routes API
Essentials covers basic routing with up to 10 intermediate waypoints. Pro adds 11 to 25 waypoints, waypoint-order optimization and traffic-aware modes. Enterprise adds two-wheel routing, toll calculation and large-vehicle routing.
Cost drivers and limits:
- Route Matrix bills per element (origins × destinations).
- Matrix requests cap at 625 elements, falling to 100 for transit or traffic-aware optimal.
- Compute Routes allows 3,000 queries per minute.
Strengths and cost watch-outs
Google's ecosystem, Places data and developer familiarity are real advantages. The risks are fragmented SKUs and costs that climb with volume.
A field-service app that geocodes 200,000 addresses a month, for instance, pays the $5 rate on the first 100,000 and $4 on the next 100,000, after the free 10,000. Work that out per SKU, not per "Maps" bill.
Mapbox, HERE, and NextBillion.ai Pricing
Mapbox pricing
Mapbox's pricing page uses a different unit for each product. Rates per 1,000, first paid band:
| Product | Unit | Free/month | First paid rate |
|---|---|---|---|
| GL JS maps | loads | 50,000 | $5 |
| Mobile maps | MAUs | 25,000 | $4 |
| Temporary Geocoding | requests | 100,000 | $0.75 |
| Permanent Geocoding | requests | none | $5 |
| Directions | requests | 100,000 | $2 |
| Matrix | elements | 100,000 | $2 |
| Optimization v1 | requests | 100,000 | $2 |
Navigation SDK v3 includes 100 MAUs free, then $0.30 per MAU, plus 1,000 free trips and $0.08 per trip after that. Temporary geocoding results cannot be cached, and permanent geocoding requires a card or enterprise contract. Vehicle and in-vehicle use requires a Commercial Application License, so ask about that cost. Matrix is capped at 25 coordinates for standard profiles and 10 for driving-traffic.
HERE pricing
HERE currently sells Base (self-service, billed per transaction with per-API free tiers) and Enterprise (MAU or asset pricing, fleet optimization, Navigate SDK). HERE's public rate table is shown in EUR, and HERE states that displayed estimates aren't final quotes. Confirm USD rates directly with HERE.
Matrix counting rules drive cost: a transaction is origins × destinations when either side has fewer than five points, otherwise 5 × the larger side. Confirm truck-routing rates, Navigate SDK list rates, and full caching terms with HERE.
NextBillion.ai pricing
NextBillion.ai publishes Basic, Advanced and Bespoke Route Planning plans with quote-based pricing. Treat any figure as a quote, not a list rate. Units are per order, per asset or per API call, and annual credits are agreement-specific. Evaluation runs two to three weeks, and the cloud, private cloud and on-premise options are all priced by quote.
Technical limits are not purchased allowances:
- Distance matrix: 1,000 × 1,000 by default, up to 5,000 × 5,000.
- Truck routing parameters: weight, dimensions, axle load, hazardous cargo.
- Optimization: time windows, capacity, skills and task relationships.
How the three differ for operational teams
For recurring routing, Mapbox gives public, per-unit tiers, HERE gives transaction billing with enterprise negotiation, and NextBillion.ai gives agreements tied to orders or assets. A quote is not directly comparable to a public API rate, so never put them in one column as equals.
Comparing the Total Cost of Maps APIs
Start with the workload
List monthly figures for:
- Map views or sessions
- Geocodes and autocomplete requests
- Route calculations and matrix cells
- Navigation users and traffic calls
- Optimization jobs, vehicles, orders and active assets
Separate interactive traffic from scheduled work. Nightly batch geocoding, route planning and polling can dwarf user-driven requests.
Normalize into scenarios
Build the same three scenarios for every provider: a consumer map app, a delivery platform and a fleet system. Write down the assumptions, billable units, free allowances and tiers, then calculate each one.
Take a simple example using public rates: 150,000 Directions requests a month. Mapbox charges for 50,000 beyond the free 100,000 at $2 per 1,000, which is $100. Google Compute Routes Essentials charges for 140,000 after 10,000 free: 90,000 at $5 plus 40,000 at $4, or $610.
These are list rates for basic routing only, and the features differ, so this isn't a "cheapest" ruling. HERE and NextBillion.ai need quotes.
Hidden and indirect costs
Support and SLAs add real money:
| Provider | Support | SLA |
|---|---|---|
| Enhanced: $500/month plus 3% of charges | 99.9% monthly | |
| Mapbox | Individual $50/month; Business 10% of spend, $500 minimum | 99.9% for covered orders |
| HERE | Developer $50/month; Essential $525; Advanced $2,200 | Depends on entitlements |
HERE also noted a 6% Essential increase from April 1, 2026 for new and renewed contracts. Beyond that, retries, matrix-size limits and orchestration raise usage while end-user volume stays flat. A 5,000 × 5,000 matrix is one call at NextBillion.ai, but it needs many chunked requests under the limits above.
Capability alongside price
A cheaper rate is poor value if you must build truck restrictions, time windows or capacity constraints yourself. NextBillion.ai lists 50+ optimization constraints and custom road attributes, which matter for logistics. Independent four-provider cost and performance studies are hard to find, so run your own tests against your workload.
Model demand growth
Calculate low, expected and high months with stated assumptions. Usage-based bills rise with seasonal spikes, fleet growth and shifts toward background route computation. Per-order or per-asset agreements trade that variability for a commitment, so compare how each handles your peak month.
Which Maps API Provider Should You Choose?
Match the provider to the workload
- Google Maps Platform: broad ecosystem, Places, and familiar tooling when you can build a detailed usage forecast.
- Mapbox: customizable web and mobile maps, with pricing tied to loads, MAUs, or requests.
- HERE: routing, traffic, navigation, and fleet needs when enterprise terms fit your process.
- NextBillion.ai: logistics, delivery, field-service and fleet software needing optimization, truck-aware routing, large matrices or flexible deployment.
Migration and implementation costs
Switching isn't free. Google returns custom JSON with lat/lng objects; Mapbox returns GeoJSON with [longitude, latitude]. Budget for SDK changes, map styling, geocoding result differences, routing behavior and testing.
Run a proof of concept first with representative addresses, vehicles, routes, constraints and peak loads.
Where NextBillion.ai fits
If per-call billing is hard to forecast because of recurring matrix workloads or complex constraints, logistics and transportation teams can evaluate NextBillion.ai's route optimization and mapping platform, including per-vehicle and fixed-monthly pricing, against their own volumes.
Frequently Asked Questions
How much does Google Maps cost?
It depends on the product, SKU, volume and any contract. Dynamic Maps lists at $7 per 1,000 loads after 10,000 free. Check Google's current pricing page.
How much does the Geocoding API cost?
Google Geocoding lists at $5 per 1,000 requests after 10,000 free per month, dropping with volume. Mapbox temporary geocoding starts at $0.75 per 1,000. Calculate from your real volume.
How much does the Google Routes API cost?
Essentials starts at $5 per 1,000 (10,000 free), Pro at $10 (5,000 free) and Enterprise at $15 (1,000 free). Matrix requests bill per element, so verify limits.
Is Google's Geocoding API free?
Only up to a cap. You get 10,000 free requests per month, then paid tiers apply, and billing must be enabled.
Is the Google Geolocation API free?
Same allowance, different service. Geolocation returns coordinates from device signals, not addresses, with 10,000 free monthly requests and $5 per 1,000 after.
