Google Maps vs Mapbox vs HERE Geocoding API (2026)

TL;DR

This is APIScout's canonical, indexable Google Maps vs Mapbox vs HERE geocoding guide. Choose Google Maps Geocoding when global address coverage, Places ecosystem integration, and enterprise familiarity matter enough to pay Google's current per-event pricing. Choose Mapbox Geocoding when a map-first app needs generous temporary geocoding usage, GeoJSON output, search UI components, and the option to pay separately for permanent storage or batch-style use. Choose HERE Geocoding & Search when logistics, routing, fleet, or enterprise location workflows matter more than a consumer map UI.

The older routing-costs page is now treated as a supporting, noindex checklist. Keep the canonical decision and source-backed pricing checks here; link to broader maps/routing pages only when the reader's problem is not primarily geocoding.

Key takeaways

Google is the safest default for address intake quality, but not the cheapest default. Google's pricing page lists Geocoding with 10,000 free monthly events and tiered per-1,000-event pricing starting at $5.00 for the first paid tier checked on June 19, 2026.
Mapbox is the easiest fit for map-first products. Mapbox's pricing page lists Temporary Geocoding with up to 100,000 monthly requests free and paid tiers starting at $0.75 per 1,000 after that threshold, plus a separate Permanent Geocoding product for storage and batch-like use cases.
HERE belongs in the shortlist for logistics and enterprise location stacks. HERE's public pricing route pushes teams to the Base Plan / contact flow, while the Geocoding & Search API docs describe the endpoint family; confirm plan-specific limits before a bulk pipeline.
Do not publish a generic accuracy winner. Run a sample set with your own countries, address formats, POIs, apartments, rural addresses, and reverse-geocode points.
Storage rights are a product decision. Temporary geocoding, permanent geocoding, autocomplete, places, routing, and map display can be separate SKUs with different rules.

Quick comparison

Decision axis	Google Maps Geocoding	Mapbox Geocoding	HERE Geocoding & Search
Best first fit	Address intake, Places ecosystem, broad global app expectations	Mapbox GL apps, search UI, GeoJSON/GIS-friendly workflows	Logistics, routing, fleet, enterprise data enrichment
Free public framing checked June 19	Geocoding SKU lists 10,000 free monthly events	Temporary Geocoding lists up to 100,000 free monthly requests	Public site says get started for free; plan details require current account/pricing review
First paid public price signal	Geocoding tier starts at $5.00 per 1,000 events after free usage	Temporary Geocoding starts at $0.75 per 1,000 after 100K requests	Confirm through HERE Base Plan or sales before modeling bulk usage
Response shape	Google JSON with `geometry.location` and `place_id`	GeoJSON features with coordinates and properties	HERE items with position and structured address fields
Autocomplete / places adjacency	Places APIs and Places UI Kit	Search Box and Search JS ecosystem	Autosuggest and Discover endpoints
Batch / storage posture	Treat as online geocoding unless a current Google SKU explicitly fits the workload	Temporary vs Permanent Geocoding are separate; Permanent supports storage and batch-oriented use cases	Often shortlisted for enterprise batch/logistics workflows; verify quota and contract terms

Authentication and basic requests

# Google Maps Geocoding API
curl "https://maps.googleapis.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&key=$GOOGLE_MAPS_API_KEY"

# Mapbox Geocoding API v6
curl "https://api.mapbox.com/search/geocode/v6/forward?q=1600+Amphitheatre+Parkway+Mountain+View+CA&access_token=$MAPBOX_ACCESS_TOKEN"

# HERE Geocoding & Search API
curl "https://geocode.search.hereapi.com/v1/geocode?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA&apiKey=$HERE_API_KEY"

Keep provider credentials server-side unless the provider's browser token model and domain restrictions are explicitly designed for your use case. For public browser maps, restrict keys by origin and API; for backend enrichment, keep keys in server secrets and add per-job budgets.

Pricing and free-tier checks

Google Maps

Google no longer needs to be described only through the old monthly-credit shorthand. The current pricing page is SKU-based: Geocoding appears under Essentials with a 10,000-event free usage cap and tiered per-1,000-event prices. That makes Google predictable for teams that already know their event volume, but it also means autocomplete, Places details, routing, maps, and address validation may add separate billable events.

Use Google when:

address quality and fuzzy matching are more important than lowest unit price;
place_id continuity matters across Places details, maps, and business data;
procurement wants a familiar global vendor with broad platform support;
the team has budget alerts, quota caps, and separate staging keys.

Mapbox

Mapbox's public pricing page separates Temporary Geocoding from Permanent Geocoding. Temporary Geocoding is the common web/mobile search case and currently lists up to 100,000 monthly requests free, followed by volume tiers. Permanent Geocoding is the product to inspect when you need to store results or run a batch-style workflow.

Use Mapbox when:

your product already uses Mapbox GL or Mapbox map styles;
the app needs a strong search/autocomplete UI with GeoJSON output;
the free temporary-geocoding allowance covers launch traffic;
you can separate temporary display use from stored or batch-enriched data.

HERE

HERE's public Base Plan page is less copy-pasteable for exact geocoding math than Google or Mapbox. Treat that as a procurement note, not a dismissal. HERE can be the right choice when geocoding is part of a logistics, route optimization, fleet, or automotive location stack and the team expects account-level terms, support, and enterprise constraints.

Use HERE when:

geocoding feeds routing, ETA, fleet, last-mile, or road-network workflows;
you need a broader HERE platform contract rather than one API endpoint;
bulk, data-enrichment, or enterprise SLA requirements matter;
you can validate plan-specific request limits before building a pipeline.

Accuracy testing methodology

Do not rely on a vendor blog, a generic benchmark, or a single address. Build a repeatable sample set before choosing:

100 clean postal addresses in your primary country;
50 messy user-entered addresses with typos, missing ZIP/postal code, or apartment/suite details;
50 rural or low-density addresses;
50 POI/business-name searches if users search for places rather than addresses;
50 reverse-geocode points near intersections, buildings, and delivery entrances;
20 international addresses for every launch country.

Score exact match, rooftop/interpolated quality, wrong-city failures, duplicate candidates, latency, rate-limit behavior, and whether the result is legally storable for your product. A provider can be best for your customer base without being universally “most accurate.”

Use-case recommendations

Use case	Better starting point	Why
Checkout or delivery address intake	Google Maps, then test Mapbox	Places and address quality often justify the price; Mapbox may be enough for specific regions.
Map-first consumer app	Mapbox	The map/search ecosystem and temporary free allowance simplify early launch.
Logistics, fleet, and route planning	HERE or Google, depending on routing stack	Geocoding quality must be evaluated with route and road-network behavior, not in isolation.
Bulk address enrichment	Mapbox Permanent Geocoding or HERE contract review	Storage/batch rights matter more than demo endpoint syntax.
Low-budget prototype	Mapbox Temporary Geocoding or a free/open alternative	Keep provider switching cheap until usage and geography are known.

Integration risk checklist

Separate autocomplete/search calls from final geocode calls so one text entry does not create unnecessary billable events.
Cache by normalized address only when the provider terms allow it; temporary geocoding often has stricter storage rules than permanent products.
Keep staging, production, and batch keys separate.
Set budget alerts before public launch.
Log request type, provider, status, latency, and chosen candidate score without storing sensitive full addresses longer than necessary.
Re-run the sample set before expanding to a new country or changing provider SKU.

Best geocoding APIs in 2026 — broader shortlist when Radar, TomTom, Positionstack, and open data belong in the discussion.
Best maps and location APIs for developers — use for map rendering, routing, geofencing, fleet, and open-source tradeoffs beyond geocoding.
Google Maps vs HERE Maps — pairwise comparison for Google ecosystem fit vs HERE logistics/enterprise fit.
Mapbox vs HERE Maps — pairwise comparison for custom maps vs fleet/location infrastructure.
APIScout Geocoding API Category

Source notes

Official sources checked on 2026-06-19:

Google Geocoding API overview: https://developers.google.com/maps/documentation/geocoding/overview
Google Maps Platform pricing list: https://developers.google.com/maps/billing-and-pricing/pricing
Mapbox Geocoding API docs: https://docs.mapbox.com/api/search/geocoding/
Mapbox pricing: https://www.mapbox.com/pricing
HERE Geocoding & Search API docs: https://www.here.com/docs/bundle/geocoding-and-search-api-developer-guide/page/README.html
HERE Base Plan pricing: https://www.here.com/get-started/pricing

Pricing, storage rights, and quota rules are volatile. Re-check the exact SKU pages before publishing a calculator, batch pipeline, or procurement recommendation.

The API Integration Checklist (Free PDF)