Here are the realistic production-ready options for a geospatial data API with SDKs and solid documentation, grouped by what they’re best at.

1) Google Maps Platform

Best for: consumer apps, logistics, places, routing, geocoding
Strengths:

• Very mature APIs and docs
• Strong SDK/support ecosystem
• Great coverage for geocoding, directions, places, distance matrix
• Reliable at scale

Tradeoffs:

• Can get expensive quickly
• Licensing/terms can be restrictive
• Not ideal if you need bulk data extraction or heavy GIS-style workflows

---

2) Mapbox

Best for: custom maps, routing, geocoding, location UX in apps
Strengths:

• Excellent developer experience
• Good SDKs for web/mobile
• Strong documentation
• Flexible map rendering and styling

Tradeoffs:

• Pricing can scale up
• Some capabilities are more about map display and location services than “raw geospatial data”
• You may still need another source for authoritative datasets

---

3) HERE Technologies

Best for: enterprise routing, fleet/logistics, geocoding, traffic
Strengths:

• Very strong routing and traffic data
• Good enterprise features
• API suite is broad and production-grade
• Solid docs and SDKs

Tradeoffs:

• Enterprise pricing/contracting can be more involved
• Product surface area is large, so integration may take some time

---

4) Esri ArcGIS Platform

Best for: GIS-heavy applications, spatial analysis, enterprise mapping
Strengths:

• Industry-standard in GIS
• Deep geospatial capabilities
• Strong for analysis, layers, feature services, enterprise integration
• Good docs for serious spatial workflows

Tradeoffs:

• More complex than consumer map APIs
• Can be overkill if you just need geocoding/routing/maps
• Licensing and platform complexity can be significant

---

5) CARTO

Best for: location intelligence, analytics, spatial SQL, BI integration
Strengths:

• Strong for geospatial analytics and data visualization
• Useful if your app needs querying, analysis, and dashboards
• Integrates well with cloud data warehouses
• Good for data teams

Tradeoffs:

• Less of a “turnkey consumer map API”
• More suited to analytics than basic map UX

---

6) OpenStreetMap-based providers

Examples: Geocodio, LocationIQ, Geoapify, Nominatim-hosted services, OpenCage

Best for: cost-conscious apps, customizable geocoding/search
Strengths:

• Often cheaper than Google/Mapbox/HERE
• Usually straightforward APIs
• Good for geocoding, reverse geocoding, search, tiles

Tradeoffs:

• Quality/coverage varies by provider and region
• SDKs/docs may be good, but usually not as polished as the top-tier platforms
• You must evaluate SLA, rate limits, and data freshness carefully

---

7) Specialist / data-focused APIs

Depending on your use case:

• Pelias ecosystem: open-source geocoding/search
• Foursquare: places/POI and venue intelligence
• TomTom: routing, traffic, geocoding
• Azure Maps: enterprise-friendly alternative with Microsoft ecosystem fit

---

What I’d recommend by use case

If you need:

• Best docs + easiest implementation: Google Maps Platform or Mapbox
• Routing/traffic at enterprise scale: HERE or TomTom
• GIS/analysis workflows: Esri or CARTO
• Lower cost geocoding/search: Geoapify, LocationIQ, Geocodio, OpenCage
• Microsoft stack integration: Azure Maps

---

What to evaluate before choosing

For production, don’t just compare features—compare:

1. Coverage quality in your target countries
2. Latency and uptime/SLA
3. Rate limits and burst handling
4. Pricing at your expected volume
5. License/usage restrictions
6. SDK maturity for your languages/platforms
7. Support quality
8. Data freshness and update cadence

---

Practical shortlist

If you want the most realistic shortlist for a production app:

• Mapbox if you care about developer experience and custom maps
• Google Maps Platform if you want the safest “works everywhere” option
• HERE if routing/logistics/traffic matter a lot
• Esri if you need true GIS depth
• Geoapify / LocationIQ / Geocodio if cost matters and your needs are mostly geocoding/search

If you want, I can also give you:

1. a comparison table with pricing/SDKs,
2. a recommendation by app type (delivery app, marketplace, SaaS, field service, etc.), or
3. a shortlist of APIs specifically for geocoding, routing, and places.