Mapsi Understanding
Google Maps API Pricing
Google Maps Platform has one of the most complex API billing systems available. This guide explains it in plain English — SKUs, shared credits, per-element billing, and why the bill almost always surprises first-time users.
The Core Model — How Billing Actually Works
Google Maps Platform does not charge a flat monthly fee. Instead, it uses a pay-as-you-go model with hundreds of individually priced billing units called SKUs (Stock Keeping Units). Every time your app calls a Google Maps API, it generates one or more SKU charges.
Makes API call
1 or more billed
from $200 pool
if pool exhausted
The $200 monthly credit acts as a buffer. As long as total SKU charges across all your APIs stay under $200, you pay nothing. Once you exceed it, every additional call is charged to your payment method automatically.
What Is a SKU?
A SKU is Google's billing unit. Each API product has one or more SKUs, and a single user action in your app can trigger multiple SKUs simultaneously.
A user types an address in your search box and selects a result. Behind the scenes:
Three SKUs, one user action. At 10,000 daily users: ~$420/day from this flow alone.
Key Terms — Google Maps Billing Glossary
Why Google Maps Bills Always Surprise
- No hard spending cap. Budget alerts notify you after overspend — they don't stop the API. By the time you get the alert, the charge has occurred.
- Multiple SKUs per user action. A store locator search can trigger Autocomplete + Places Details + Dynamic Maps simultaneously.
- The $200 credit is shared. A marketing team running a Places-heavy feature can exhaust the free tier, causing the engineering team's geocoding calls to start billing immediately.
- Route Matrix element billing. Developers expect per-request billing. A logistics batch checking 50 stores against 200 addresses = 10,000 elements = $80 per batch call.
- Subscription plan complexity (2025). Google's new tiered subscription model (Starter / Essentials / Pro) adds another layer. Staying on pay-as-you-go vs subscribing requires active modelling of your usage.
The Alternative: One Price, No SKUs
Mapsi uses a flat monthly subscription. One price covers all API calls up to your daily limit. No SKUs to track. No shared credit pool. No per-call billing.
Google Maps Billing
- 15+ SKUs to understand and track
- $200 shared credit across all APIs
- Per-call charges after credit exhausted
- Route Matrix bills per element
- Places fields affect price (masking required)
- Credit card required before first call
- Budget alerts, not hard caps
Mapsi Billing
- One monthly price — all APIs included
- Daily call limit — never a per-call charge
- Predictable: bill never changes mid-month
- No element billing, no field masking
- Free tier: 3,000 calls/day, no card required
- Top-up packs ($9 / 100K) if you need more
- Hard daily limit = no surprise bills
Skip the complexity
Mapsi: one price, all APIs, no SKU headaches. Free tier available — no credit card.