# ArcGIS Location Platform vs Azure Maps

> Azure Maps scores 67.9 (B) on agent readiness against ArcGIS Location Platform's 65.4 (B), and leads in 4 of 7 scored categories. ArcGIS Location Platform leads on agent ergonomics, payments & pricing and maintenance & community. Both do geo geocode. ArcGIS Location Platform is…

- Canonical: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps
- Markdown: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.md (~2,650 tokens)
- Slim: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Azure Maps scores 67.9 (B) on agent readiness against ArcGIS Location Platform's 65.4 (B), and leads in 4 of 7 scored categories. ArcGIS Location Platform leads on agent ergonomics, payments & pricing and maintenance & community. Both do geo geocode. ArcGIS Location Platform is cheaper for geo geocode, $0.50 against $4.50 per 1,000 requests.

- ArcGIS Location Platform: grade B, 65.4/100, rank #259 of 722. Markdown https://www.anchorterminal.com/tools/arcgis.md · JSON https://www.anchorterminal.com/api/v1/tools/arcgis.json
- Azure Maps: grade B, 67.9/100, rank #196 of 722. Markdown https://www.anchorterminal.com/tools/azure-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-maps.json

## Which one, for what

### ArcGIS Location Platform (B)

Good for: Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.

Ahead on:
- Agent ergonomics, 78 against 73
- Payments & pricing, 40 against 20
- Maintenance & community, 83 against 67

Also in its favour:
- Cheaper for geo geocode, $0.50 against $4.50 per 1,000 requests

Watch for: The agreement bars benchmarking availability, performance or functionality, and publishing benchmark results, without prior written permission from Esri and its licensors (sections 3.1.b.6 and 3.1.c.6.F).

### Azure Maps (B)

Good for: Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price.

Ahead on:
- Reliability, 81 against 65
- Schema & documentation, 83 against 61

Watch for: Place and category search exist only in Search 1.0. Search 2026-01-01, which supersedes it, has geocoding, autocomplete, reverse geocoding and polygons


## Score by category

| Category | Weight | ArcGIS Location Platform | Azure Maps | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 81 | Azure Maps +16 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 83 | Azure Maps +22 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 73 | ArcGIS Location Platform +5 |
| Security & auth | 14% (17.5 this run) | 64 | 66 | Azure Maps +2 |
| Payments & pricing | 10% (12.5 this run) | 40 | 20 | ArcGIS Location Platform +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 67 | ArcGIS Location Platform +16 |
| Transparency & trust | 7% (8.8 this run) | 72 | 74 | Azure Maps +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.4 · B** | **67.9 · B** | |

## Facts side by side

| Fact | ArcGIS Location Platform | Azure Maps |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Esri | Microsoft Azure |
| Hosted endpoint | `https://geocode-api.arcgis.com` | `https://atlas.microsoft.com` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for geo geocode | $0.50 per 1,000 requests | $4.50 per 1,000 requests |
| x402 | no | no |
| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-29 | 2026-09-30 |
| Terms last updated |  | no date given |
| Privacy policy last updated | 2026-07-31 | 2026-09-01 |
| Customer content may train models |  | yes |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |
| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | 9.1k npm/wk, 25k PyPI/wk |

## Verdicts

**ArcGIS Location Platform.** Per-unit prices are public for every service, with a monthly free tier of 20,000 geocodes and 20,000 routes, keys limited to chosen privileges and a 99.9 per cent SLA. No rate limits or OpenAPI description were found, results may not be stored unless the dearer stored geocode is bought, and the agreement bars benchmarking without written permission.

**Azure Maps.** Azure Maps publishes OpenAPI documents for every service, per-service rate limits, a 99.9 per cent SLA and written rules on storing results, and Entra ID roles can limit a caller to one service. Place search exists only in Search 1.0, which the newer version has superseded, and the REST client libraries are all beta.

## Before you call either

### ArcGIS Location Platform

1. Send the token in an `X-Esri-Authorization: Bearer` or `Authorization` header. The docs' examples put it in a `token` parameter, which Esri's own best-practice page calls less secure.
2. Set `forStorage=true` on `findAddressCandidates` or `reverseGeocode` only when results will be kept. It needs pay-as-you-go and the Geocode (stored) privilege, and costs eight times the unstored rate.
3. Cap geocoding output with `maxLocations` (default and maximum 50) and `outFields`, because billing counts results returned and the default returns every field.
4. Page place searches with `pageSize` (maximum 20) and `offset`. A nearby or extent search costs $8 per 1,000 requests after 500 free a month.
5. Check the JSON body for an `error` object with `code`, `message` and `details`. Code 499 means the token is missing and 403 means it lacks the privilege.

### Azure Maps

1. Send the key in the `subscription-key` header, or use `Authorization: Bearer` with `x-ms-client-id`. The key also works as a URL parameter, which leaks into logs.
2. Call `GET /geocode?api-version=2026-01-01` for addresses. It can return 200 with no results, so check `confidence`, `matchCodes` and the entity type before use.
3. Use Search 1.0 (`/search/poi/json`, `/search/nearby/json`, `/search/fuzzy/json`) for places. The 2026-01-01 version has no place search.
4. Use `eu.atlas.microsoft.com` or `us.atlas.microsoft.com` to keep request data in that geography.
5. Don't store route or tile results beyond six months, and never for serving several users. The product terms allow keeping geocodes while the account is active.

## Questions

### Which is better for AI agents, ArcGIS Location Platform or Azure Maps?

Azure Maps scores 67.9 (B) on agent readiness against ArcGIS Location Platform's 65.4 (B), and leads in 4 of 7 scored categories. ArcGIS Location Platform leads on agent ergonomics, payments & pricing and maintenance & community.

### Which is cheaper for geo geocode, ArcGIS Location Platform or Azure Maps?

ArcGIS Location Platform, at $0.50 per 1,000 requests against $4.50 per 1,000 requests for Azure Maps. These are the vendors' published prices for the job.

### Do ArcGIS Location Platform and Azure Maps need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call ArcGIS Location Platform and Azure Maps without installing anything?

Yes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and Azure Maps at https://atlas.microsoft.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.json, and with the fewest tokens: https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "arcgis", "b": "azure-maps"}`. From a terminal: `anchor compare arcgis azure-maps`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/arcgis.json and https://www.anchorterminal.com/api/v1/tools/azure-maps.json

## Other comparisons with ArcGIS Location Platform or Azure Maps

- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)
- [Amazon Location Service vs Azure Maps](https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md)
- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)
- [ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform.md)
- [ArcGIS Location Platform vs LocationIQ](https://www.anchorterminal.com/compare/arcgis-vs-locationiq.md)
- [ArcGIS Location Platform vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-mapbox.md)
- [ArcGIS Location Platform vs MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)
- [ArcGIS Location Platform vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/arcgis-vs-opencage.md)
- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)
- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)
- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)
- [Azure Maps vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/azure-maps-vs-google-maps-platform.md)
- [Azure Maps vs LocationIQ](https://www.anchorterminal.com/compare/azure-maps-vs-locationiq.md)
- [Azure Maps vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-mapbox.md)
- [Azure Maps vs MapQuest](https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.md)
- [Azure Maps vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/azure-maps-vs-opencage.md)
- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)
- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)