Geocoding API: Complete Guide to Features, Pricing & Use Cases

Q: Which geocoding API is most accurate?

Google leads at 99.9% accuracy globally. HERE and TomTom match or beat Google in specific regions — TomTom in Europe, HERE in Asia. Free alternatives like Nominatim run around 70-80% accuracy. For production use cases where errors cost money, paid providers are worth it.

Businesses lose $8.2 billion globally every year because of bad location data. Wrong coordinates. Failed deliveries. Broken map features. And most of the time, the root cause is the same: picking the wrong geocoding API — or not understanding what one actually does.

This guide covers everything you need to know. What a geocoding API is, how the top providers compare, what they cost, and which one fits your use case.

What Is a Geocoding API?

A geocoding API converts a human-readable address into geographic coordinates — latitude and longitude. You send "350 Fifth Avenue, New York, NY 10118," you get back 40.7484, -73.9967. That's it.

Computers don't understand street names. They need numbers. Every map feature, delivery route, and location search you've ever used runs on this conversion behind the scenes.

Forward vs. Reverse Geocoding

There are two directions:

Forward geocoding — address in, coordinates out. You type a location, the API returns a lat/lng pair. This powers search boxes, address validation, and store locators.

Reverse geocoding — coordinates in, address out. A user taps a point on a map, and the API tells you what's there. This powers delivery tracking, ride-sharing pickups, and "what's near me" features.

Most real applications need both. Forward for input forms, reverse for map interactions.

How It Works Under the Hood

Geocoding APIs run against massive geographic databases — collections of address records, road networks, and place names. When you send a query, the API parses it, normalizes it (handling typos, abbreviations, missing zip codes), and matches it against that database.

Good APIs hit 95%+ accuracy on US addresses. Free or lower-quality services land around 70-80%. That gap matters when you're validating thousands of addresses at scale.

Top Geocoding API Providers in 2025

The geocoding market hit $20.6 billion in 2023 and is projected to reach $38.5 billion by 2028. Here's who's worth knowing.

Google Geocoding API

Google is the default choice for most developers. It covers 99.9% of addresses worldwide, handles messy input well, and integrates with the rest of Google's mapping stack.

The catch: it costs $5 per 1,000 requests after the free tier. Google gives you 10,000 free requests per month — which sounds like a lot until you realize a mid-sized e-commerce site burns through that in days. Amazon validates 500+ million addresses per year. At Google's rates, that's a serious bill.

There's also a data retention limit: you can only store Google geocoding results for 30 days. Go beyond that without a separate agreement, and you're violating their terms.

Mapbox Geocoding API

Mapbox is popular with developers who want control over the visual layer. You can style everything — colors, fonts, map tiles — to match your brand. Accuracy in urban areas is close to Google's. Response times for business accounts run 50-100ms.

Pricing is more competitive at $0.75 per 1,000 requests. The tradeoff: rural and international coverage is thinner than Google or HERE.

Free Geocoding APIs

Several solid free options exist for smaller projects:

OpenCage — 2,500 requests per day, free. Paid plans start at $0.50 per 1,000.
Nominatim (OpenStreetMap) — completely free, but rate-limited hard. Not for production traffic.
Google's free tier — 10,000 requests/month. Fine for prototypes.

The consistent tradeoff: free APIs respond in 200-500ms. Paid enterprise APIs hit 50-100ms. On a map where users expect instant results, that difference is noticeable.

Enterprise Geocoding: HERE and TomTom

For high-volume or specialized use cases, HERE Technologies and TomTom are the serious options.

HERE covers 99%+ of the world and includes features Google doesn't bother with — truck routing that accounts for bridge heights, weight limits, and hazmat restrictions. TomTom dominates in Europe, with more granular address data than Google in many markets.

Enterprise pricing drops to $0.10-0.30 per 1,000 requests at 10M+ monthly volume. That's a fraction of Google's rate.

Geocoding API Pricing Comparison

Here's a direct comparison of what you'll actually pay:

Provider	Free Tier	Paid Rate	Data Retention
Google	10,000/month	$5.00 per 1,000	30 days max
Mapbox	100,000/month	$0.75 per 1,000	Flexible
HERE	Limited	$0.50+ per 1,000	Permanent
OpenCage	2,500/day	$0.50 per 1,000	Permanent
TomTom	2,500/day	$0.50+ per 1,000	Permanent

The math is stark. Google charges $5 per 1,000 requests. Alternatives start at $0.50 — that's 90% cheaper at the same volume. At 1 million requests per month, you're looking at $5,000 with Google vs. $500 with alternatives. Same accuracy tier.

Real-World Use Cases

E-commerce Address Validation

Amazon validates 500+ million addresses per year. The result: 23% fewer failed deliveries, saving an estimated $2.1 billion annually. Geocoding catches bad addresses before a package ships — wrong apartment numbers, nonexistent streets, transposed zip codes.

For any online store, address validation at checkout pays for itself. One returned package costs more in logistics and customer service than months of API fees.

Logistics and Route Optimization

DoorDash integrated real-time geocoding and cut average delivery times from 38 minutes to 32 minutes. Six minutes per delivery, across millions of orders, adds up to a measurable revenue increase.

FedEx and UPS go further — they layer elevation data, traffic patterns, and weather on top of basic geocoding. North America accounts for 35% of global geocoding API usage, driven almost entirely by logistics.

Real Estate and Property Search

Zillow geocodes 150+ million property addresses. Here's the telling stat: 67% of their searches start on the map, not the search bar. Two out of three users navigate visually first. If your coordinates are off, your listings are wrong.

Reverse geocoding powers the "what's nearby" features that users expect — schools, transit, restaurants. That context influences decisions.

Travel and Hospitality

Booking.com geocodes hotels in 220+ countries. Location data influences 89% of bookings. "How far from the beach?" "Hotels near the airport?" Every one of those queries runs through geocoding.

Reverse geocoding handles the tap-to-explore behavior: a user drops a pin on a map and expects to see what's there instantly. Apps that can't do this feel broken in 2025.

How to Choose the Right Geocoding API

There's no single best option. The right choice depends on your volume, geography, and use case.

If you're prototyping or building something small: Use free tiers. OpenCage's 2,500 daily requests or Google's 10,000 monthly are enough to validate your idea without spending anything. Speed and accuracy don't matter yet — just get it working.

If you're running an e-commerce store: Prioritize accuracy over price. One failed delivery costs more than a month of premium API fees. Google or HERE are the safe choices, especially for international addresses.

If you're doing high volume: Negotiate. At 10M+ monthly requests, enterprise pricing from HERE or TomTom drops to $0.10-0.30 per 1,000 — a fraction of Google's rate. Run the numbers before defaulting to Google.

If you're building a mobile app: Response time matters more than anything. Users won't wait 500ms for a location result. Pay for 50-100ms enterprise APIs and cache aggressively.

By geography:

North America: Google or Mapbox
Europe: TomTom (better granularity than Google in many markets)
Asia-Pacific: HERE Technologies (fastest-growing region)
Global coverage: Google is the safest default at 99%+ worldwide

Implementation Best Practices

Even the right API fails if you implement it poorly.

Respect rate limits. Google caps at 50 requests per second. Hit that ceiling and your app stops responding. Build retry logic. Cache results. Don't hammer the API with redundant requests.

Handle failures gracefully. APIs go down. Addresses don't exist. Internet connections drop. Never let a geocoding failure crash your entire application. Have a fallback — if your primary provider fails, queue the request for retry or fall back to a secondary service.

Batch your requests. If you have 10,000 addresses to geocode, don't send them one at a time. Batch APIs process them in bulk — faster and cheaper. Some providers charge less per request for batch jobs.

Add confidence scoring. An API returning coordinates doesn't mean those coordinates are right. Most geocoding APIs return a confidence score or accuracy level. Flag low-confidence results for manual review. This matters especially for medical deliveries, emergency services, or anything where a wrong address has real consequences.

Read the data retention terms. Google: 30 days maximum. OpenCage, HERE, TomTom: store permanently. Violating storage policies can get your account banned. If you're building a location database, pick a provider that lets you keep the data.

What Geocoding APIs Don't Tell You

Geocoding converts addresses to coordinates. It doesn't tell you anything about the businesses at those locations — what they do, how many reviews they have, whether they have a website, or what technologies they use.

That's a different problem. If you're doing local business prospecting or lead generation, you need business data on top of location data. IBLead covers 50M+ businesses across 37 countries, with 50+ data fields per listing — including addresses, phone numbers, emails, Google ratings, review counts, and 160+ detected web technologies. The data is pre-indexed and updated weekly, so you export instantly without waiting for a scrape to run.

For $52, you get 10,000 business contacts — that's $0.004 per lead. Start free — 200 credits, no card required

FAQ

What's the difference between geocoding and reverse geocoding?

Forward geocoding converts an address to coordinates. Reverse geocoding does the opposite — you provide lat/lng and get back a street address. Most applications use both: forward for search inputs, reverse for map interactions where users tap or click.

Which geocoding API is most accurate?

Google leads at 99.9% accuracy globally. HERE and TomTom match or beat Google in specific regions — TomTom in Europe, HERE in Asia. Free alternatives like Nominatim run around 70-80% accuracy. For production use cases where errors cost money, paid providers are worth it.

Are there free geocoding APIs worth using?

Yes, for small projects. OpenCage gives you 2,500 requests per day free. Google gives 10,000 per month. Nominatim is unlimited but throttled. The consistent tradeoff is speed: free APIs respond in 200-500ms vs. 50-100ms for paid tiers. For prototypes, free works fine. For production with real users, the latency difference is noticeable.

How much does a geocoding API cost at scale?

It varies widely. Google charges $5 per 1,000 requests. Mapbox charges $0.75. HERE and TomTom start around $0.50 and drop to $0.10-0.30 at enterprise volume (10M+ monthly). The difference between Google and alternatives at scale can be 90% savings — thousands of dollars per month for high-volume applications.

Can I store geocoding results permanently?

Depends on the provider. Google limits storage to 30 days unless you have a separate data agreement. OpenCage, HERE, and TomTom allow permanent storage. Always read the terms before building a location database — violating storage policies can result in account termination.