Geoapify
Geoapify · Ranked #8 of 8 in Maps & Geocoding APIs
Lean OSM-based geocoding/routing/places platform with an interactive playground, free batch geocoding, and fully self-serve credit-based pricing.
Affordable OSM-based geocoding & maps

Overview
Geoapify is a Vienna-based location platform that packages OpenStreetMap-derived data (plus OpenAddresses, GeoNames and other open datasets) into a developer-friendly REST API suite: forward and reverse geocoding, address autocomplete, batch geocoding, Places/POI search, routing and route optimization, distance/time matrices, map matching, isochrones/isolines, IP geolocation, elevation, and raster/vector map tiles plus static maps. It positions itself as an affordable, privacy-respecting alternative to Google Maps and Mapbox, and its key commercial differentiator is permissive licensing: because the data is open, customers are allowed to cache and store geocoding results, which is contractually forbidden on Google and many commercial providers. Pricing is unified under a single credit currency (1 geocoding or autocomplete request = 1 credit; map tiles = 0.25 credit), which makes cross-API budgeting simple.
The target user is a developer or small-to-mid team that needs solid, cost-controlled location functionality without negotiating an enterprise contract. The free tier (3,000 credits/day, 5 req/s) is genuinely usable for prototypes and light production, and paid tiers scale linearly from $59/mo to $609/mo before reaching custom/dedicated-server plans. Geoapify ships first-party front-end components, a Geocoder Autocomplete JS/TS library with React and Angular wrappers, a Route Planner SDK, and map integrations for Leaflet, MapLibre GL, OpenLayers and QGIS, which lowers integration effort for web apps. The interactive API Playground and code samples (JS, Node, Python) are frequently cited strengths.
Where Geoapify wins is price-to-value, OSM-based global coverage, cache-friendly licensing, and ease of onboarding. Where it loses is at the precision frontier: like all OSM-backed geocoders, address-level accuracy and rooftop precision in some regions trail Google, and reviewers note occasional mis-geocoded or unresolved addresses and the per-request/rate-limit ceilings on lower tiers when processing very large datasets. The published SLA is modest (99.5% on paid plans, with service-credit remedies below that), and there is no prominent public real-time status page, which is a gap for buyers who need transparent reliability reporting. For mapping, routing and high-volume geocoding where "good and affordable" beats "best and expensive," it is a strong pick; for mission-critical rooftop accuracy in dense commercial use cases, teams should benchmark it against Google/Mapbox on their own address sets first.
How this score is derived
The APIbenchmarks Index is a weighted sum of four dimensions, each scored on an absolute 0–100 reference scale. See the methodology for every mapping.
| Dimension | Score | Weight | Contribution |
|---|---|---|---|
| Documentation & DXStrong: dedicated API docs site (apidocs.geoapify.com) with an interactive Playground, per-endpoint references, and JS/Node/Python code samples plus a GitHub code-samples repo. | 75 | 30% | 22.5 |
| ReliabilityModest and somewhat opaque: paid plans carry a 99.5% monthly SLA with tiered service-credit remedies, but there is no prominent official real-time status/uptime page. | 68 | 25% | 17.0 |
| Ecosystem & SDKsGood for a mid-size vendor: first-party Geocoder Autocomplete library with React/Angular wrappers, a Route Planner SDK, npm packages, and integrations for Leaflet, MapLibre GL, OpenLayers and QGIS. | 58 | 25% | 14.5 |
| AccessibilityVery accessible: no-credit-card free tier (3,000 credits/day), self-serve API-key signup, unified credit pricing, and a free interactive playground lower the barrier to entry. | 92 | 20% | 18.4 |
| APIbenchmarks Index (ABI) | 72.4 | ||
Table 1. Derivation of the ABI for Geoapify. Contribution = score × weight; the index is their sum.
At a glance
- Vendor
- Geoapify
- Pricing model
- Per credit (per req)
- Free tier
- 3k credits/day (free plan)
- Official SDKs
- 9 languages
Pricing
| Free | $0/mo | 3,000 credits/day, up to 5 requests/second, no credit card required |
| API 10 | $59/mo | 10,000 credits/day, up to 12 requests/second |
| API 25 | $109/mo | 25,000 credits/day, up to 15 requests/second |
| API 50 | $179/mo | 50,000 credits/day, up to 20 requests/second |
| API 100 | $299/mo | 100,000 credits/day, up to 25 requests/second |
| API 250 / Custom | $609/mo; Custom from $860/mo | 250,000 credits/day at up to 30 req/s; Custom adds unmetered credits and dedicated servers (e.g. up to 50 req/s geocoding) |
Key features
- •Forward & reverse geocoding with single and batch requests
- •Address Autocomplete API with type/country/language filtering and location bias
- •Places (POI) API filterable by area, category and geometry
- •Routing API for single vehicles and multi-stop fleet route optimization
- •Route Matrix API (distance/time between many points)
- •Isochrone / isodistance (isolines) for drive, truck, walk and transit modes
- •Map matching (snap GPS traces to roads)
- •Vector & raster map tiles, static maps, and marker-icon API
- •IP geolocation and elevation/terrain APIs
- •Permissive open-data licensing allowing result caching and storage
Official SDKs
Strengths & trade-offs
- +Cache-friendly licensing: OSM-based data may be stored/cached, unlike Google Maps which forbids it
- +Unified, predictable credit pricing (1 geocoding request = 1 credit; map tiles = 0.25 credit) across all APIs
- +Generous no-credit-card free tier (3,000 credits/day) usable for prototypes and light production
- +Async batch geocoding cuts per-call cost by up to 50% (0.5 credit coefficient)
- +First-party front-end components: Geocoder Autocomplete with React/Angular wrappers, Route Planner SDK, Leaflet/MapLibre/OpenLayers support
- +Broad single-vendor API coverage: geocoding, routing, matrix, isolines, places, map tiles, IP geolocation
- –OSM-backed accuracy can trail Google for rooftop precision and some addresses fail to resolve
- –Lower tiers cap rate at 5-15 req/s, which can bottleneck very large dataset processing
- –Modest 99.5% SLA and no prominent public real-time status page for transparent uptime reporting
- –Smaller third-party community/ecosystem than Google Maps or Mapbox
- –Routing cost model (per waypoint pair plus distance surcharges over 500 km) is less simple than the flat geocoding pricing
What developers say
Reviewers consistently praise Geoapify for ease of use, quick setup, affordability and OSM-based accuracy, while a minority flag per-request/rate limits on large datasets and occasional addresses that fail to geocode.
“I use Geoapify for geocoding locations, solving the problem of not having latitudes and longitudes. It's quick, easy to use, and straightforward.”
Key figures
| Free plan quota / rate limit | 3,000 credits/day, 5 requests/second | Geoapify pricing page ↗ |
| Max rate limit (standard plans) | Up to 30 requests/second (API 250); up to 50 req/s on dedicated custom servers | Geoapify pricing page ↗ |
| Geocoding price point | 1 credit per geocoding request (0.5 in async batch) | Geoapify pricing details ↗ |
| Map tile price point | 0.25 credit per tile (4 tiles = 1 credit) | Geoapify pricing details ↗ |
| Availability SLA (paid plans) | 99.5% monthly; 10% credit below 99.5%, 50% credit below 99% | Geoapify terms / SLA ↗ |
Compare Geoapify head to head
Sources
- https://www.geoapify.com/pricing/
- https://www.geoapify.com/pricing-details/
- https://www.geoapify.com/
- https://apidocs.geoapify.com/
- https://www.geoapify.com/downloads/
- https://www.geoapify.com/terms-and-conditions/
- https://www.g2.com/products/geoapify/reviews
- https://www.capterra.com/p/204775/Geoapify/
Figures last verified 2026-06-27. Spotted an error? corrections@apibenchmarks.com
