We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
MapTiler Cloud is our best overall pick for teams adding maps to apps: its listed Flex plan starts at $30 per month, though quotas need checking. HERE Technologies and Foursquare suit broader location-data needs, but their published pricing details are limited. Geocodio is a practical option for address lookups, while Radar adds location and fraud tools with an annual-commitment caveat. CARTO is stronger for spatial analysis than a straightforward maps API, and MapKit JS has too little product detail for a confident recommendation. Compare usage limits and total cost before switching.
Quick picksThe shortlist
MapTiler CloudMapTiler CloudBest overall · $30/mo
HERE TechnologiesHERE TechnologiesBest for advanced mapping · Free
FoursquareFoursquareBest for venue data · $25/mo
RadarRadarBest for location tools · $0.02/mo
GeocodioGeocodioBest for geocoding · Free
CARTOCARTOBest for spatial analysis · Custom
MapKit JSMapKit JSBest for MapKit access · $8.25/mo
01Compared at a glance
| Tool | Score | From | Free plan | Trial |
|---|---|---|---|---|
| MapTiler CloudMapTiler Cloud | 6.5 | $30/mo | Yes | — |
| HERE TechnologiesHERE Technologies | 7.0 | Free | Yes | — |
| FoursquareFoursquare | 6.9 | $25/mo | Yes | 30 days |
| RadarRadar | 7.0 | $0.02/mo | No | — |
| GeocodioGeocodio | 6.8 | Free | Yes | — |
| CARTOCARTO | 6.2 | Custom | No | 30 days |
| MapKit JSMapKit JS | 4.5 | $8.25/mo | No | — |
02The picks, in detail
- Best overallMapTiler CloudMapTiler Cloud
MapTiler Cloud is the clearest general-purpose pick here for developers adding maps to apps or building custom styles. Its listed Flex plan starts at $30 per month, and a free plan is available. The main caution is quotas: check the plan limits against expected usage before committing, especially if your app serves maps at scale or needs offline deployment.
What works
- Ready-to-use street, satellite and topographic maps
- Custom map design tools
- SDKs for interactive, static and 3D maps
What doesn't
- Flex costs $30/month before VAT
- Flex includes 25,000 sessions per month
- Flex includes 3,000 search sessions per month
- Best for advanced mappingHERE TechnologiesHERE Technologies
HERE Technologies is worth shortlisting for location-aware applications, fleet and tour routing, and automotive projects. A free plan is listed, but a starting paid price is not published on the vendor's site. That makes projected usage and a direct pricing check important before comparing it with a fixed-price alternative. It is a better fit for specialized needs than buyers seeking simple cost certainty.
What works
- Free monthly allowances cover several API services
- Includes routing, geocoding, search, and map tiles
- Tour Planning supports complex fleet routes
What doesn't
- No flat monthly or annual starting price is published
- Enterprise pricing and usage limits are not published
- Overage rates vary by service and volume
- Best for venue dataFoursquareFoursquare
Foursquare fits teams that need real-world location signals, venue data, or a starting point for spatial analysis. The listed starting price is $25, with a free plan available. The tradeoff is that usage bands and analysis caps can affect value, so check the limits for your expected workload before committing. It is less of a straightforward choice if your main need is basic app mapping.
What works
- Basic Spatial Desktop plan is free through 2026
- Standard costs $25/month
- Places API Pro tier includes 0–500 calls at $0 CPM
What doesn't
- Places API pricing changes by endpoint and volume
- No annual subscription rates are listed
- Standard caps use at 200 simple or 30 complex analyses
- Best for location toolsRadarRadar
Radar combines maps APIs with location and fraud tools, making it a fit for teams that need arrival detection or location signals for fraud prevention. Its listed starting price is $0.02, but the published details do not specify the billing unit. Annual commitments also make it more expensive to try. Confirm the pricing basis and commitment terms before comparing that headline price with alternatives.
What works
- Core Maps includes geocoding, autocomplete, and static maps
- Directions, distances, and matrix are listed
- Premium Maps adds address validation and places search
What doesn't
- No free plan is listed
- Agreements require annual commitments
- Monthly quotas apply
- Best for geocodingGeocodioGeocodio
Geocodio is a focused option for occasional address lookups, spreadsheet processing without code, and geocoding in its supported regions. A free tier is listed, but paid prices are not published on the vendor's site. Confirm both regional coverage and likely paid costs before moving a larger workload. Its appeal is strongest when geocoding is the job, rather than when you need a broader mapping platform.
What works
- 2,500 free lookups per day, forever
- Pay-as-you-go credits never expire
- Spreadsheet processing requires no code
What doesn't
- Paid plan prices aren't published in the published details
- Flex monthly credit amounts aren't published
- Distance API credits cost extra
- Best for spatial analysisCARTOCARTO
CARTO is built for teams analyzing spatial data in the cloud, using low-code workflows, or building spatial apps. That makes it a better fit for analysis-heavy work than a basic map display. Its starting price is not published on the vendor's site, which is a real hurdle for buyers comparing budgets. Ask for pricing and scope before shortlisting it against tools with listed entry plans.
What works
- More than 100 ready-to-use analysis components
- Native ML and AI integrations
- Low-code, drag-and-drop analysis
What doesn't
- Starting price is not published
- Committed plans require upfront annual billing
- Pay As You Go has limited API access and tokens
- Best for MapKit accessMapKit JSMapKit JS
MapKit JS is for developers who specifically need MapKit JS access and whose usage fits the listed daily caps. Its listed starting price is $8.25, but the published details do not specify the billing period. Annual billing and limited product detail make it difficult to judge value against broader options. Check the caps, billing terms, and feature fit before treating the low entry price as a clear saving.
What works
- Apple Developer Program is $99 annually
- Daily map-view allowance is listed
- Service-call allowance is listed
What doesn't
- Published Apple homepage doesn’t describe MapKit JS
- Monthly billing price is not published
- Overage and seat costs are not published
03How we chose
We weigh published pricing, plan limits, documentation, and Reddit sentiment because those sources help show both the cost of an API and the work it may take to adopt. We look for clear usage allowances, overage terms, and documentation that explains the relevant endpoints and restrictions. Reddit comments can flag practical concerns, but they are anecdotal, not a substitute for product documentation. The published published material does not include vendor-specific prices or limits, so we do not rank these tools by cost or claim a feature advantage without evidence.
04Choose an API around the location job
Start with the job your product needs done: maps, geocoding, location data, or a location-aware application. Then write down the required inputs, outputs, coverage, and expected request volume. This makes comparisons between CARTO, Radar, MapTiler Cloud, Foursquare, HERE Technologies, Geocodio, and MapKit JS less dependent on broad feature lists.
Check the documentation for endpoint behavior, supported data formats, authentication, errors, and usage restrictions. Confirm that the API covers the places and workflows your users need; do not treat a general claim of geographic coverage as proof that a particular use case is supported. If a requirement is unclear in the docs, ask the vendor before building around it. A small shortlist based on required tasks is more useful than choosing the provider with the longest feature page.
05Price the workload—and the cost of switching
Compare the expected bill at your own usage level, not just the entry price. Record the published price, included usage, plan limits, and any stated overage terms for each provider. If a rate or cap is not published, mark it as unknown and ask sales or support; do not assume it is unlimited or included.
Before switching, inventory the places where the current API is embedded: application code, stored location data, keys, billing alerts, and operational documentation. Check how much of that can move directly and what needs a new implementation. Plan a limited rollout and a way to revert if the new provider does not meet requirements. Reddit reports may reveal issues worth investigating, but they are anecdotal; verify important claims against current documentation and your own requirements.
Questions people ask
How should we choose a mapping API?
Start with the specific task—maps, geocoding, location data, or a location-aware application—and list required coverage, request volume, and technical constraints. Compare documentation and published plan limits against that list. The right shortlist depends on your workload, not a general feature count.
Which of these mapping APIs is cheapest?
The published published material does not include comparable current prices or usage limits for CARTO, Radar, MapTiler Cloud, Foursquare, HERE Technologies, Geocodio, or MapKit JS. We cannot name a cheapest option. Compare each provider's published pricing against your expected usage and confirm any unpublished rates directly.
What should we check before switching mapping providers?
Inventory API calls, stored location data, keys, billing rules, and application dependencies. Then check the new provider's documentation for endpoint behavior, limits, and errors. Test the migration with a limited rollout and keep a rollback path until the new setup meets your requirements.
Can Reddit reviews tell us which provider to pick?
Reddit comments can point to questions worth investigating, such as unexpected limits or implementation friction. They are individual reports, not verified product specifications. Confirm claims in the provider's current documentation or pricing information, and ask the provider when a requirement is not clearly documented.