Google Maps Platform integration and API pricing

How Google prices the Maps APIs

Google Maps Platform is pay-as-you-go. Every API product is a SKU with a price per 1,000 billable events, and usage is added up across all projects linked to one billing account each month. As of October 2026:

• SKUs sit in three categories: Essentials, Pro and Enterprise.
• Each SKU has free monthly usage. At global rates that is 10,000 events for Essentials, 5,000 for Pro and 1,000 for Enterprise. Google's FAQ says this replaced the old USD 200 monthly credit on 1 March 2025. The allowance resets on the first of each month, Pacific time.
• India has its own price list, in effect since 1 August 2024, for accounts with billing in India and a large majority of usage in India. Its free usage is 70,000, 35,000 and 7,000 events, and it has one price up to 5 million events.
• Volume discounts apply automatically at global rates, with lower prices above 100,000 events a month.
• Subscriptions exist (Starter at $100 for 50,000 calls a month, Essentials at $275 for 100,000, Pro at $1,200 for 250,000), but Google's page excludes customers eligible for India pricing.

Prices are in US dollars on both lists; Google bills new India-based customers in rupees.

A worked monthly cost

Take a delivery business with a dispatcher dashboard and a customer tracking page. In one month it uses 150,000 web map loads, 120,000 autocomplete requests (billed per request, no sessions), 90,000 geocoding requests and 200,000 basic route calculations.

The global column drops the first 10,000 events of each SKU, charges the next 90,000 at the first tier and the rest at the 100,001 to 500,000 tier, which is how Google's own example on the pricing page is worked. At half this volume on India pricing, autocomplete and geocoding would both fall inside the free allowance and cost nothing.

Data that flows each way

The main flow, step by step

1. Create a Google Cloud project and a billing account, with India as the billing country if you qualify.
2. Enable only the APIs the product needs.
3. Create a separate key for each app, with an application restriction and an API restriction on each.
4. Render maps in the client with the Maps JavaScript API or the mobile SDK. Call Routes and Geocoding from your server with a server-side key.
5. Use session tokens with autocomplete, and end each session with one details request.
6. Set quotas and budget alerts before launch.

Rules and gotchas Google documents

• A map load is billed when the map is created. Google's usage page says a map load triggers the Dynamic Maps SKU; panning and zooming afterwards do not add loads.
• Autocomplete sessions change the bill. A session that ends in Place Details Pro, Enterprise or Address Validation makes its autocomplete requests free. One that ends in Place Details Essentials bills the first 12 requests.
• Geocoding results shown on a map must be shown on a Google map. The policy page also restricts caching, with one exception: place IDs can be stored indefinitely.
• Unrestricted keys are your liability. Google holds the account owner financially responsible for charges from key abuse.
• Features decide the SKU. Google's Routes billing page bills basic requests with up to 10 intermediate waypoints as Essentials, traffic-aware routing as Pro, and two-wheel routing as Enterprise. A delivery app that routes for motorbikes is on the dearest of the three.

Common failures follow from these: a web key copied from the page source and used by someone else, a map re-created on every screen change, geocoding the same address on every page view instead of once at order time, and autocomplete firing on every keystroke with no session token.

Lower-cost alternatives

Checked on each provider's own site on 2 October 2026:

What WavX builds around it

Maps, GPS and live tracking are part of mobile app development at WavX, and of products such as fleet management software for logistics businesses. For a client who needs maps, WavX builds:

• Address capture with autocomplete, session tokens and a stored place ID.
• Server-side routing, distance and ETA, with results saved so the same route is not bought twice.
• Live tracking that sends driver positions through your own server and moves a marker without reloading the map.
• Restricted keys, quotas and budget alerts, plus a usage report by SKU.
• A provider layer, so a map or routing provider can be swapped without rewriting the app.

WavX does not publish a price for a single integration; it is quoted after scoping. For planning, the software cost estimator carries third-party integrations as a ₹60,000 feature line on top of a base build. Its output is a planning range, not a quote. The wider offer is under API and system integration services, and ride-hailing costs are worked through in the cost to build an app like Uber.

When you do not need a developer

• A map on a contact page. Maps Embed is listed with unlimited free usage. Paste the embed code.
• Directions to your shop. A link to Google Maps costs nothing.
• A store locator with a few branches. Many site builders include one.

Custom integration earns its cost when location is part of the product: dispatch, delivery tracking, service-area checks, or fares that depend on distance.