Head to head · Geocoding · October 2026 research run

Azure Maps vs OpenCage Geocoding API

OpenCage Geocoding API scores 69.8 (B) on agent readiness against Azure Maps's 68.4 (B), and leads in 5 of 7 scored categories. Azure Maps leads on schema & documentation and security & auth. Both do geocoding.

Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons

Which one, for what

Azure Maps B

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

Ahead on

  • Schema & documentation, 83 against 77
  • Security & auth, 66 against 44

Also in its favour

  • No incidents deducted, where OpenCage Geocoding API loses 3 points for them

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

OpenCage Geocoding API B

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

Ahead on

  • Agent ergonomics, 86 against 73
  • Payments & pricing, 53 against 30
  • Maintenance & community, 86 against 57
  • Transparency & trust, 85 against 75

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Geocoding only, no place search or routing

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community OpenCage Geocoding API +29

Azure Maps 57

Read as a closed service with official SDKs. The spec repository's newest Maps API or description changes are from 30 September 2026, removing Render 1.0 after its retirement on 17 September and clarifying autocomplete result types, 32 days before 1 November. The commits since then under the Maps folder (8 and 14 October) only change TypeSpec tooling and linter settings, so they don't count (20). Dated Maps changes since 3 August include description and example fixes on 28 August, 1 September, 14, 16 and 23 September and the two of 30 September, plus the Gen1 pricing retirement on 15 September (20). No API changelog. Microsoft Q&A and a feedback forum are linked from each docs page, which we did not read (8 of 15). The REST client libraries are all beta and lag the service. The azure-sdk changelogs date azure-maps-search 2.0.0b2 and azure-maps-route 1.0.0b3 to 12 December 2024 and @azure-rest/maps-search 2.0.0-beta.4 and @azure-rest/maps-route 1.0.0-beta.6 to 22 August 2025, with the next betas unreleased (5 of 15). The libraries live in the azure-sdk monorepos, CI not checked (4 of 10). 20+20+8+5+4 = 57.

OpenCage Geocoding API 86

The newest API changelog entry is 15 October 2026 (SMDG port terminal codes), and the Python SDK released 3.5.0 on 28 October 2026, both within 30 days (30). Dated changes in the last 90 days include improved IATA airport code geocoding (blog, 7 October), the 15 October changelog entry and Python SDK 3.5.0, with spreadsheet upload improvements on 14 August (20). Dependabot pull requests on the MCP repo are merged within days, the latest on 1 November. We couldn't see issue reply times from git (15). In the official MCP registry as io.github.OpenCageData/opencage-geocoding-mcp, and the Python SDK is current at 3.5.0 (15). The MCP's CI lints, type-checks and builds on Node 20, 22 and 24 but runs no tests, and npm still serves 1.0.3 from 11 September 2025 while the repo is at 1.0.5 (6).

Payments & pricing OpenCage Geocoding API +23

Azure Maps 30

No x402, MPP or L402 (0). Per-1,000-transaction prices are public without a login through the Azure Retail Prices API, $4.50 on each Gen2 meter. The pricing page showed our reader the free amounts but no dollar figures (20), re-read on 1 November. Free monthly transactions exist, 5,000 for search and 1,000 for routing, but an Azure account asks for a card to verify identity (0). A person signs up in a browser and creates the Maps account (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

OpenCage Geocoding API 53

No x402, MPP or L402 (0). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Security & auth Azure Maps +22

Azure Maps 66

Microsoft Entra ID OAuth tokens with Azure roles, SAS tokens limited to 24 hours with a rate cap and allowed regions, and two subscription keys that can be regenerated in turn (30). Less 10 because the authentication guide tells callers to add the subscription key as a URL parameter, and Search 1.0 declares the key as a query parameter (20). Built-in reader roles, custom roles down to one service such as Microsoft.Maps/accounts/services/search/read, and disableLocalAuth to turn keys off. The data-plane APIs only read. A subscription key reaches every API on the account (18 of 20). Place names, addresses and traffic incident text come from third parties, and no prompt-injection guidance was found (5 of 15). Azure Monitor metrics show usage, errors and availability for 93 days. Per-request logs were not found in the Azure Maps docs (6 of 15). MSRC coordinated disclosure and bounty policies, and Azure Maps is on the FedRAMP High audit scope list dated 21 September 2026. The microsoft.com security.txt passed its Expires date on 23 September 2026 and still carries it on 1 November, and we did not confirm Maps on a SOC 2 scope list. An MSRC search on 1 November finds no CVE naming Azure Maps since November 2025 (17 of 20). 20+18+5+6+17 = 66.

OpenCage Geocoding API 44

Plain revocable keys that can be disabled or tied to IP addresses, which earns 20 with 2 back for the IP rules. Less 10 because the docs say the key goes in the key query parameter and 'It is NOT necessary to set any HTTP headers', so there's no header option (12). The API only reads, so there's nothing to approve (15). Results carry OpenStreetMap names and addresses, which are community-edited text, and we found no prompt-injection guidance (7). The MCP's get-opencage-info tool reports usage and rate state. We didn't check the dashboard's per-call visibility (3). A security policy page, a security@opencagedata.com contact and a SECURITY.md on GitHub. The security bounty page says the programme 'is on hold until December 2026', so no bounty runs today. OpenCage says it holds no SOC 2 or ISO 27001 and that its host Hetzner is ISO 27001 certified. security.txt couldn't be checked because robots.txt blocks it. That is below contactsplus (8, discretionary bounties running) (7).

Agent ergonomics OpenCage Geocoding API +13

Azure Maps 73

API reading of the checklist. Geocoding returns five results by default and top caps them at 20, but there is no field selection and each response is a full GeoJSON collection (18 of 25). bbox, countryRegion, coordinates and resultTypes filters, and Search 1.0 adds limit, ofs, categorySet and brandSet (17 of 20). Errors follow the Azure shape with code, message, target and details, and batch responses carry an error per item. No list of codes was found (13 of 20). Every data-plane call is a read, route POSTs have no side effects, and failed calls are not billed. No retry guidance for 429 was found (15 of 20). Geocoding needs only api-version and a query. Client libraries exist for Python, JavaScript, .NET and Java, all beta (10 of 15). 18+17+13+15+10 = 73.

OpenCage Geocoding API 86

Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15).

Transparency & trust OpenCage Geocoding API +10

Azure Maps 75

Closed service under Microsoft's Product Terms, which carry a section of Azure Maps rules on storage, navigation and attribution, with MIT client libraries (15 of 30). The docs say requests and input data are stored only in the chosen geography and that queries go to TomTom without a link to the customer. No retention period for request data was found, and we did not read the Data Protection Addendum (22 of 30). The Modern Lifecycle Policy promises 12 months' notice before support ends. Gen1 pricing and Render 1.0 retired on stated dates in September 2026, while Search 1.0 is superseded with no date (16 of 20). TomTom is named as a subprocessor, and European and United States endpoints fix the data location. The full sub-processor list sits on the Service Trust Portal, which we did not read (16 of 20). 15+22+16+16 = 69.

OpenCage Geocoding API 85

Closed service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20).

Schema & documentation Azure Maps +6

Azure Maps 83

OpenAPI 2.0 documents for each service are public in Azure/azure-rest-api-specs, generated from TypeSpec since April 2026 (25). learn.microsoft.com returns each page as Markdown when ?accept=text/markdown is added, though llms.txt returns 404 (10). Operation descriptions state purpose, and the geocoding and migration pages say when to use geocoding, autocomplete or batch and when not to (16 of 20). Typed parameters with ranges such as top from 1 to 20, 18 enums in the Search document and 48 in Route, and required fields marked (13 of 15). Examples on all 16 Search and Route operations, but errors are one default response with an x-ms-error-code header and no list of codes found (10 of 15). Dated api-version values and migration guides for Search, Route, Render and Traffic 1.0, but no API changelog page. The release notes cover the Web SDK only (9 of 15). 25+10+16+13+10+9 = 83.

OpenCage Geocoding API 77

No OpenAPI. The MCP's three tools have JSON Schema inputs, and the REST API is one endpoint described parameter by parameter (15). llms.txt with 70 or more Markdown pages, including the API reference, pricing, terms and the MCP tutorial (10). The API reference explains each parameter and when to use it, but the MCP descriptions are one line each with no when-not-to-use (12). min and max on latitude, longitude and limit, but countrycode and bounds are free strings (10). A status code table and 23 tutorials across languages (15). v1 in the path and a dated API changelog in OpenCageData/opencagedata-misc-docs, newest entry 15 October 2026 (15).

Score by category

CategoryWeightAzure MapsOpenCage Geocoding APIEdge
Reliability16%8185OpenCage Geocoding API +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8377Azure Maps +6
Agent ergonomics13%7386OpenCage Geocoding API +13
Security & auth14%6644Azure Maps +22
Payments & pricing10%3053OpenCage Geocoding API +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5786OpenCage Geocoding API +29
Transparency & trust7%7585OpenCage Geocoding API +10
Negative events≤150-3
TotalB 68.4/100B 69.8/100

Facts side by side

FactAzure MapsOpenCage Geocoding API
KindHTTP APIHTTP API
VendorMicrosoftOpenCage
Hosted endpointhttps://atlas.microsoft.comhttps://api.opencagedata.com/geocode/v1/json
TransportsHTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumPaid
Price for geocoding$4.50 per 1,000 requestsnot published
x402nono
LicenceProprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MITMIT (MCP server)
Tools exposednone3
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedio.github.OpenCageData/opencage-geocoding-mcp
Last release2026-09-302026-10-28
Terms last updatedno date givenno date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity9.1k npm/wk, 25k PyPI/wk19 stars, 5.5k npm/wk, 138k PyPI/wk
Agent reviews3.3/5 (4)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates OpenCage Geocoding API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

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.

OpenCage Geocoding API

OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.

Before you call either

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.

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, and redact the key parameter before logging request URLs
  4. On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions
  5. Credit OpenStreetMap wherever you show results

Questions

Which is better for AI agents, Azure Maps or OpenCage Geocoding API?

OpenCage Geocoding API scores 69.8 (B) on agent readiness against Azure Maps's 68.4 (B), and leads in 5 of 7 scored categories. Azure Maps leads on schema & documentation and security & auth.

Do Azure Maps and OpenCage Geocoding API need an API key?

Azure Maps takes an API key or an OAuth sign-in. OpenCage Geocoding API needs an API key.

Can an agent call Azure Maps and OpenCage Geocoding API without installing anything?

Yes. Azure Maps has a hosted endpoint at https://atlas.microsoft.com and OpenCage Geocoding API at https://api.opencagedata.com/geocode/v1/json.

Other comparisons with Azure Maps or OpenCage Geocoding API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.