# ArcGIS Location Platform vs OpenCage Geocoding API

> OpenCage Geocoding API scores 69.2 (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 security & auth, payments & pricing and maintenance & community. Both do geo geocode. Category scores…

- Canonical: https://www.anchorterminal.com/compare/arcgis-vs-opencage
- Markdown: https://www.anchorterminal.com/compare/arcgis-vs-opencage.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/arcgis-vs-opencage.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/arcgis-vs-opencage.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

OpenCage Geocoding API scores 69.2 (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 security & auth, payments & pricing and maintenance & community. Both do geo geocode.

- 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
- OpenCage Geocoding API: grade B, 69.2/100, rank #164 of 722. Markdown https://www.anchorterminal.com/tools/opencage.md · JSON https://www.anchorterminal.com/api/v1/tools/opencage.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:
- Security & auth, 64 against 47
- Payments & pricing, 40 against 35
- Maintenance & community, 83 against 66

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).

### OpenCage Geocoding API (B)

Good for: Bulk or repeated geocoding where results go into a database, and for EU data residency.

Ahead on:
- Reliability, 85 against 65
- Schema & documentation, 77 against 61
- Agent ergonomics, 86 against 78
- Transparency & trust, 84 against 72

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: Geocoding only, no place search or routing


## Score by category

| Category | Weight | ArcGIS Location Platform | OpenCage Geocoding API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 85 | OpenCage Geocoding API +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 77 | OpenCage Geocoding API +16 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 86 | OpenCage Geocoding API +8 |
| Security & auth | 14% (17.5 this run) | 64 | 47 | ArcGIS Location Platform +17 |
| Payments & pricing | 10% (12.5 this run) | 40 | 35 | ArcGIS Location Platform +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 66 | ArcGIS Location Platform +17 |
| Transparency & trust | 7% (8.8 this run) | 72 | 84 | OpenCage Geocoding API +12 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.4 · B** | **69.2 · B** | |

## Facts side by side

| Fact | ArcGIS Location Platform | OpenCage Geocoding API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Esri | OpenCage |
| Hosted endpoint | `https://geocode-api.arcgis.com` | `https://api.opencagedata.com/geocode/v1/json` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| Price for geo geocode | $0.50 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | MIT (MCP server) |
| Tools exposed | 8 | 3 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.OpenCageData/opencage-geocoding-mcp` |
| Last release | 2026-09-29 | 2026-06-25 |
| Terms last updated |  | no date given |
| Privacy policy last updated | 2026-07-31 | no date given |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | not found in the text |
| 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 | 19 stars, 5.5k npm/wk, 138k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

## 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.

**OpenCage Geocoding API.** Permanent storage of results on every plan, including after you cancel. Geocoding only, no place search or routing.

## 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.

### OpenCage Geocoding API

1. Add no_annotations=1 and limit=1 when you only need coordinates
2. Stop on 402, which means the day's quota is gone, and back off on 429
3. Add no_record=1 when the query holds personal data
4. Redact the key parameter before logging request URLs
5. Credit OpenStreetMap wherever you show results

## Questions

### Which is better for AI agents, ArcGIS Location Platform or OpenCage Geocoding API?

OpenCage Geocoding API scores 69.2 (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 security & auth, payments & pricing and maintenance & community.

### Do ArcGIS Location Platform and OpenCage Geocoding API need an API key?

ArcGIS Location Platform takes an API key or an OAuth sign-in. OpenCage Geocoding API needs an API key.

### Can an agent call ArcGIS Location Platform and OpenCage Geocoding API without installing anything?

Yes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and OpenCage Geocoding API at https://api.opencagedata.com/geocode/v1/json.


## For agents

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

## Other comparisons with ArcGIS Location Platform or OpenCage Geocoding API

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