{ "data": { "a": { "slug": "azure-maps", "name": "Azure Maps", "vendor": "Microsoft Azure", "vendorUrl": "https://azure.microsoft.com/en-us/products/azure-maps", "kind": "http-api", "category": "maps", "summary": "Microsoft Azure's mapping service. Its REST APIs at `atlas.microsoft.com` cover geocoding, reverse geocoding, place search, routing with traffic, map tiles, time zones and weather, with access by subscription key, SAS token or Microsoft Entra ID.", "url": "https://www.anchorterminal.com/tools/azure-maps", "markdownUrl": "https://www.anchorterminal.com/tools/azure-maps.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-maps.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-maps.json", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "transports": [ "http" ], "remoteUrl": "https://atlas.microsoft.com", "packages": [ { "registry": "pypi", "name": "azure-maps-search" }, { "registry": "pypi", "name": "azure-maps-route" }, { "registry": "npm", "name": "@azure-rest/maps-search" }, { "registry": "npm", "name": "@azure-rest/maps-route" } ], "auth": "mixed", "authNotes": "Self-serve. A person creates an Azure subscription and an Azure Maps account in the portal, which issues a primary and a secondary subscription key. The key goes in the `subscription-key` header or as a URL parameter and reaches every REST API on the account. Microsoft Entra ID tokens (scope `https://atlas.microsoft.com/.default`, with the `x-ms-client-id` header) are authorised by Azure roles such as Azure Maps Data Reader or a custom role for one service. SAS tokens (`Authorization: jwt-sas`) last 24 hours at most and carry a rate cap and allowed regions. `disableLocalAuth` turns keys and SAS tokens off.", "pricing": "freemium", "pricingNotes": "$4.50 per 1,000 transactions on every Gen2 meter, after a free monthly amount of 5,000 transactions for Search, Geolocation, Timezone and base map tiles and 1,000 for Routing, Traffic, Weather, imagery tiles and static images (https://prices.azure.com/api/retail/prices, read 8 October 2026). Fifteen tiles count as one transaction, four route matrix cells as one, and ten autocomplete requests as one. The pricing page says discounts start at 100,000 transactions a month through sales. An Azure account needs a card for identity checks, so there is no card-free start. Gen1 pricing retired on 15 September 2026.", "priceSummary": "$4.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Azure Maps docs, the OpenAPI documents or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 9084, "pypiWeekly": 24564, "asOf": "2026-10-08" }, "docsUrl": "https://learn.microsoft.com/en-us/rest/api/maps/", "openapi": "https://github.com/Azure/azure-rest-api-specs/blob/main/specification/maps/data-plane/Search/stable/2026-01-01/search.json", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles", "weather.current", "weather.forecast" ], "tags": [ "hosted", "closed-source", "freemium", "free-tier", "card-required", "openapi", "oauth", "python", "typescript", "dotnet", "java", "enterprise", "sla", "eu" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 67.9, "grade": "B", "agentReady": false, "rank": 236, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 67, "payments": 20, "reliability": 81, "schema": 83, "security": 66, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price.", "strengths": [ "Public OpenAPI documents for Search, Route, Render, Traffic, Weather, Timezone and Geolocation in `Azure/azure-rest-api-specs`, with examples on every operation", "Three credential types. Entra ID with built-in and custom roles, SAS tokens with a 24-hour limit, a rate cap and allowed regions, and two rotatable keys", "Default rate limits published per service, 500 requests a second for search, 250 for reverse geocoding and 50 for routing", "The product terms state storage rules in writing. Geocodes may be kept while the Azure account is active, other results for six months at most", "Responses with 5xx, 401, 403, 408 and 429 are not billed, and the October 2026 SLA commits to 99.9 per cent" ], "weaknesses": [ "Place and category search exist only in Search 1.0. Search 2026-01-01, which supersedes it, has geocoding, autocomplete, reverse geocoding and polygons", "Every REST client library is a beta. `azure-maps-search` on PyPI was last released on 12 December 2024", "The authentication guide tells callers to put the subscription key in the URL, and the key reaches every REST API on the account", "An Azure account needs a card and a browser signup before the free monthly transactions apply", "No Retry-After header or backoff guidance for 429 was found in the reviewed documentation, and no API changelog page" ], "agentNotes": [ "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.", "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.", "Use Search 1.0 (`/search/poi/json`, `/search/nearby/json`, `/search/fuzzy/json`) for places. The 2026-01-01 version has no place search.", "Use `eu.atlas.microsoft.com` or `us.atlas.microsoft.com` to keep request data in that geography.", "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." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.9 } ], "editorialScores": { "ergonomics": 73, "maintenance": 67, "payments": 20, "reliability": 81, "schema": 83, "security": 66, "transparency": 69 }, "provenanceScore": 78 }, "connect": { "install": "pip install azure-maps-search # or: npm i @azure-rest/maps-search", "http": "curl \"https://atlas.microsoft.com/geocode?api-version=2026-01-01\u0026query=15127%20NE%2024th%20Street%2C%20Redmond%2C%20WA\" \\\n -H \"subscription-key: $AZURE_MAPS_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/azure-maps" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "power-automate", "foundry-local", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "everyday", "unitPrices": [ { "item": "Search (geocoding, reverse geocoding, places)", "unit": "1k-requests", "usd": 4.5, "note": "5,000 free a month. Ten autocomplete requests count as one" }, { "item": "Routing", "unit": "1k-requests", "usd": 4.5, "note": "1,000 free a month. Four matrix cells count as one" }, { "item": "Base map tiles", "unit": "1k-requests", "usd": 4.5, "note": "5,000 free a month. One transaction is 15 tiles" }, { "item": "Traffic", "unit": "1k-requests", "usd": 4.5, "note": "1,000 free a month" }, { "item": "Weather", "unit": "1k-requests", "usd": 4.5, "note": "1,000 free a month" }, { "item": "Static map images", "unit": "1k-requests", "usd": 4.5, "note": "1,000 free a month" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "The API answers at atlas.microsoft.com, with eu.atlas.microsoft.com and us.atlas.microsoft.com for a chosen geography. Docs are on learn.microsoft.com.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA", "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Product Terms page for Microsoft Azure carries the Azure Maps service-specific terms (navigation, database, caching and storage, attribution, print and broadcast rules) and points to the Data Protection Addendum and the SLA. Our reader saw no effective date on the page.", "The privacy statement (last updated September 2026) names Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052, and Microsoft Ireland Operations Limited in Dublin. It lists Microsoft Azure among the enterprise online services and says the customer's agreement controls where the two conflict.", "No changelog for the REST APIs was found in the Azure Maps docs. The release notes there cover the Web SDK map control, drawing tools and spatial module only, and the docs link to the general Azure updates page.", "https://www.microsoft.com/.well-known/security.txt shows Expires 2026-09-23T16:00:00.000Z. It points to the MSRC researcher portal, the bounty policy and the coordinated disclosure policy.", "RDAP for microsoft.com gives a registration date of 1991-05-02.", "The Azure status page is shared by all Azure services and its history lists only broad incidents." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-maps.json", "live": { "slug": "azure-maps", "probe": { "target": "https://atlas.microsoft.com", "method": "get", "lastAt": "2026-10-10T02:07:01.470293153Z", "lastOk": true, "lastStatus": 200, "lastMs": 597, "authRequired": false, "uptime24h": 92.4, "uptime30d": 92.55, "p50ms24h": 315, "p95ms24h": 733, "samples24h": 250, "samples30d": 322, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 45 }, { "date": "2026-10-09", "probes": 250, "ok": 233 }, { "date": "2026-10-10", "probes": 22, "ok": 20 } ], "outages": [ { "start": "2026-10-09T21:15:56.246049703Z", "end": "2026-10-09T21:34:12.491890137Z", "note": "HTTP 503 server error" } ] }, "versions": [ { "registry": "npm", "name": "@azure-rest/maps-route", "version": "1.0.0-beta.5", "seenAt": "2026-10-09T16:41:50.985227054Z" }, { "registry": "npm", "name": "@azure-rest/maps-search", "version": "2.0.0-beta.3", "seenAt": "2026-10-09T16:41:50.001025557Z" }, { "registry": "pypi", "name": "azure-maps-route", "version": "1.0.0b3", "released": "2024-12-12", "seenAt": "2026-10-09T16:41:48.179006303Z" }, { "registry": "pypi", "name": "azure-maps-search", "version": "2.0.0b2", "released": "2024-12-12", "seenAt": "2026-10-09T16:41:47.918940067Z" } ], "githubStars": 3100, "npmWeekly": 6893, "pypiWeekly": 24496, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "expired", "expires": "2026-09-23T16:00:00.000Z", "checkedAt": "2026-10-09T15:40:16.790821018Z" }, "pages": [ { "url": "https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA", "kind": "terms", "status": 502, "checkedAt": "2026-10-09T18:52:20.023098983Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-10T02:07:01.470293153Z" } }, "answer": "Azure Maps scores 67.9 (B) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.", "b": { "slug": "radar", "name": "Radar", "vendor": "Radar Labs", "vendorUrl": "https://radar.com", "kind": "http-api", "category": "maps", "summary": "Radar is a location platform from Radar Labs with REST APIs for forward, reverse and IP geocoding, address autocomplete and validation, places search, distance, matrix, directions and route optimisation, plus geofencing, trip tracking and base maps.", "url": "https://www.anchorterminal.com/tools/radar", "markdownUrl": "https://www.anchorterminal.com/tools/radar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/radar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/radar.json", "repo": "https://github.com/radarlabs/radar-sdk-js", "license": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.radar.io/v1", "packages": [ { "registry": "npm", "name": "radar-sdk-js" } ], "auth": "api-key", "authNotes": "API key in the `Authorization` header, with no query-string option documented. Each project has four keys, test and live, publishable and secret. Publishable keys reach 16 of the 36 documented operations, including all geocoding, search and routing calls, and can be restricted by website domain or mobile app identifier. Secret keys reach the rest and can read or write any data. Keys come from the dashboard. Whether sign-up is self-serve was not established, because dashboard.radar.com's robots.txt closes every path.", "pricing": "paid", "pricingNotes": "Core Maps (forward, reverse and IP geocoding, autocomplete, static maps, distance, directions, matrix) starts at $0.50 per 1,000 API calls and Premium Maps (address validation, places search, route matching, route optimisation, satellite maps) at $2.00. Matrix bills per element. Every plan is an annual commitment with a monthly quota, at a rate Radar sets by quote. The pricing page says there is no free tier, and that teams can start with a technical validation period arranged with sales (https://radar.com/pricing).", "priceSummary": "$0.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the docs index or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.radar.com/api", "llmsTxt": "https://docs.radar.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "api-key", "llms-txt", "status-page", "sales-led", "annual-contract", "soc2", "closed-source" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 53.3, "grade": "D", "agentReady": false, "rank": 713, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 77, "payments": 10, "reliability": 70, "schema": 50, "security": 56, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "9 October 2026. The Maps product page says the geocoding APIs come with 'the right to store, reuse, and export results freely' (https://radar.com/product/maps), while section 2(d) of the Terms of Use forbids storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days (https://radar.com/terms) and the geocoding docs repeat the 30-day limit (https://docs.radar.com/maps/geocoding.md). 2 points for a claim the published terms contradict. A quoted enterprise agreement may differ and is not published." ], "verdict": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.", "bestFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.", "strengths": [ "Each of the 36 documented operations states its key level and a default rate limit, from 10 to 100 requests a second", "docs.radar.com publishes llms.txt and a Markdown twin of every page, including the whole API reference in one file", "Statuspage history lists two API incidents in the 90 days to 9 October 2026, of 3 minutes and about an hour", "Publishable keys are limited to 16 client-safe operations and can be restricted by website domain or mobile app identifier", "The DPA names two sub-processors (AWS and MongoDB) and the FAQ states default retention periods" ], "weaknesses": [ "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote", "No OpenAPI description and no API changelog were found in the docs index", "The terms cap storage of geocoding, autocomplete and place results at 30 days, while the Maps product page claims a right to store results freely", "The terms of 24 May 2023 let Radar change or stop the services without notice, and still describe a free version", "A secret key can read or write any project data, with no scopes found", "The terms forbid using the services to develop or test other geocoding, autocomplete or place search APIs, which matters before any probe is run" ], "agentNotes": [ "Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com", "Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons", "Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses", "Set `units=metric` on routing calls. The default is imperial, with distances in feet", "Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented", "Do not keep geocoding, autocomplete or place results for more than 30 days" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.3 } ], "editorialScores": { "ergonomics": 65, "maintenance": 77, "payments": 10, "reliability": 70, "schema": 50, "security": 56, "transparency": 51 }, "provenanceScore": 58 }, "connect": { "install": "npm install radar-sdk-js", "http": "curl \"https://api.radar.io/v1/geocode/forward?query=20+jay+st+brooklyn+ny\" -H \"Authorization: $RADAR_PUBLISHABLE_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/radar" }, "area": "everyday", "unitPrices": [ { "item": "Core Maps API calls, starting price", "unit": "1k-requests", "usd": 0.5, "note": "Geocoding, autocomplete, static maps, distance, directions, matrix (per element). Annual commitment, rate set by quote" }, { "item": "Premium Maps API calls, starting price", "unit": "1k-requests", "usd": 2, "note": "Address validation, places search, route matching, route optimisation, satellite maps. Annual commitment, rate set by quote" } ], "provenance": { "legalEntity": "Radar Labs, Inc.", "domain": "radar.com", "domainRegistered": "1994-12-16", "endpointOnVendorDomain": false, "terms": "https://radar.com/terms", "privacy": "https://radar.com/privacy", "statusPage": "https://status.radar.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The privacy notice (last updated 13 May 2025) names Radar Labs, Inc., a Delaware corporation at 111 5th Ave, 12th Floor, New York, NY 10003.", "The Terms of Use (last updated 24 May 2023) cover the SDK and Radar's APIs and incorporate the DPA at radar.com/dpa. They describe a free version, which the pricing page says Radar does not have. Paid plans are by quote, and no enterprise agreement is published.", "The API answers at api.radar.io, a second domain. Nothing was sent to it, and its registrant was not checked.", "radar.com/.well-known/security.txt answers 404. The FAQ gives security@radar.com for reports.", "No API changelog was found in the docs index. The web SDK repository has dated release tags.", "RDAP gives 16 December 1994 as the registration date of radar.com.", "robots.txt answers on the day. radar.com 200 with a sitemap line only. docs.radar.com 200 with ai-input=yes. status.radar.com 200 disallowing /api/ and /embed/. dashboard.radar.com 200 disallowing every path. trust.radar.com answers the request with its page shell." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/radar.json", "live": { "slug": "radar", "probe": { "target": "https://api.radar.io/v1", "method": "get", "lastAt": "2026-10-10T02:07:21.733773078Z", "lastOk": true, "lastStatus": 404, "lastMs": 120, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 124, "p95ms24h": 233, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "vendorStatus": { "page": "https://status.radar.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:06:25.849384695Z" }, "versions": [ { "registry": "github", "name": "radarlabs/radar-sdk-js", "version": "autocomplete-v1.1.1", "released": "2026-09-14", "seenAt": "2026-10-09T17:15:51.370576682Z" }, { "registry": "npm", "name": "radar-sdk-js", "version": "5.2.0", "seenAt": "2026-10-09T17:15:50.510226325Z" } ], "githubStars": 52, "npmWeekly": 62814, "pages": [ { "url": "https://radar.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:44:14.0723216Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22ff53a04e1c" }, { "url": "https://radar.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:44:16.223416673Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "12f29204b40d" }, { "url": "https://radar.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:44:18.136602575Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "411754a84910" } ], "updatedAt": "2026-10-10T02:07:21.733773078Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft Azure", "b": "Radar Labs", "name": "Vendor" }, { "a": "https://atlas.microsoft.com", "b": "https://api.radar.io/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "$4.50 per 1,000 requests", "b": "not published", "name": "Price for geocoding" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "b": "Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-09-14", "name": "Last release" }, { "a": "no date given", "b": "2023-05-24", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2025-05-13", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "9.1k npm/wk, 25k PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Azure Maps scores 67.9 (B) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Azure Maps or Radar?" }, { "answer": "Azure Maps takes an API key or an OAuth sign-in. Radar needs an API key.", "question": "Do Azure Maps and Radar need an API key?" }, { "answer": "Yes. Azure Maps has a hosted endpoint at https://atlas.microsoft.com and Radar at https://api.radar.io/v1.", "question": "Can an agent call Azure Maps and Radar without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 81 against 70", "Schema \u0026 documentation, 83 against 50", "Agent ergonomics, 73 against 65", "Security \u0026 auth, 66 against 56", "Payments \u0026 pricing, 20 against 10", "Transparency \u0026 trust, 74 against 55" ], "also": null, "goodFor": "Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price.", "slug": "azure-maps", "watchFor": "Place and category search exist only in Search 1.0. Search 2026-01-01, which supersedes it, has geocoding, autocomplete, reverse geocoding and polygons" }, { "aheadOn": [ "Maintenance \u0026 community, 77 against 67" ], "also": null, "goodFor": "A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.", "slug": "radar", "watchFor": "The pricing page says Radar has no free tier and every plan is an annual commitment set by quote" } ], "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.json", "title": "Amazon Location Service vs Azure Maps", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-radar.json", "title": "Amazon Location Service vs Radar", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.json", "title": "ArcGIS Location Platform vs Azure Maps", "url": "https://www.anchorterminal.com/compare/arcgis-vs-azure-maps" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-radar.json", "title": "ArcGIS Location Platform vs Radar", "url": "https://www.anchorterminal.com/compare/arcgis-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.json", "title": "Azure Maps vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-geoapify" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-google-maps-platform.json", "title": "Azure Maps vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.json", "title": "Azure Maps vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-locationiq.json", "title": "Azure Maps vs LocationIQ", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-mapbox.json", "title": "Azure Maps vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.json", "title": "Azure Maps vs MapQuest", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-opencage.json", "title": "Azure Maps vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.json", "title": "Azure Maps vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.json", "title": "Azure Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-radar.json", "title": "Geoapify Location Platform + MCP vs Radar", "url": "https://www.anchorterminal.com/compare/geoapify-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.json", "title": "Google Maps Platform + Grounding Lite MCP vs Radar", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json", "title": "HERE Location Services vs Radar", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-radar.json", "title": "LocationIQ vs Radar", "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-radar.json", "title": "Mapbox APIs + MCP vs Radar", "url": "https://www.anchorterminal.com/compare/mapbox-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-radar.json", "title": "MapQuest vs Radar", "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-radar.json", "title": "OpenCage Geocoding API vs Radar", "url": "https://www.anchorterminal.com/compare/opencage-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps.json", "title": "Radar vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json", "title": "Radar vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom" } ], "scores": [ { "azure-maps": 81, "by": 11, "edge": "azure-maps", "key": "reliability", "name": "Reliability", "radar": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-maps": 83, "by": 33, "edge": "azure-maps", "key": "schema", "name": "Schema \u0026 documentation", "radar": 50, "weight": 13 }, { "azure-maps": 73, "by": 8, "edge": "azure-maps", "key": "ergonomics", "name": "Agent ergonomics", "radar": 65, "weight": 13 }, { "azure-maps": 66, "by": 10, "edge": "azure-maps", "key": "security", "name": "Security \u0026 auth", "radar": 56, "weight": 14 }, { "azure-maps": 20, "by": 10, "edge": "azure-maps", "key": "payments", "name": "Payments \u0026 pricing", "radar": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-maps": 67, "by": 10, "edge": "radar", "key": "maintenance", "name": "Maintenance \u0026 community", "radar": 77, "weight": 7 }, { "azure-maps": 74, "by": 19, "edge": "azure-maps", "key": "transparency", "name": "Transparency \u0026 trust", "radar": 55, "weight": 7 } ], "summary": "Azure Maps scores 67.9 (B) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community. Both do geocoding.", "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.", "radar": "Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/azure-maps-vs-radar", "json": "https://www.anchorterminal.com/compare/azure-maps-vs-radar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-maps-vs-radar.md", "slim": "https://www.anchorterminal.com/compare/azure-maps-vs-radar.min.md" }, "markdown": "Azure Maps scores 67.9 (B) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community. Both do geocoding.\n\n- Azure Maps: grade B, 67.9/100, rank #236 of 950. Markdown https://www.anchorterminal.com/tools/azure-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-maps.json\n- Radar: grade D, 53.3/100, rank #713 of 950. Markdown https://www.anchorterminal.com/tools/radar.md · JSON https://www.anchorterminal.com/api/v1/tools/radar.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### Azure Maps (B)\n\nGood for: Teams already on Azure that want geocoding and routing under Entra ID roles and one flat price.\n\nAhead on:\n- Reliability, 81 against 70\n- Schema \u0026 documentation, 83 against 50\n- Agent ergonomics, 73 against 65\n- Security \u0026 auth, 66 against 56\n- Payments \u0026 pricing, 20 against 10\n- Transparency \u0026 trust, 74 against 55\n\nWatch 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\n\n### Radar (D)\n\nGood for: A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.\n\nAhead on:\n- Maintenance \u0026 community, 77 against 67\n\nWatch for: The pricing page says Radar has no free tier and every plan is an annual commitment set by quote\n\n\n## Score by category\n\n| Category | Weight | Azure Maps | Radar | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 81 | 70 | Azure Maps +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 50 | Azure Maps +33 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 65 | Azure Maps +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 56 | Azure Maps +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 10 | Azure Maps +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 77 | Radar +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 74 | 55 | Azure Maps +19 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **67.9 · B** | **53.3 · D** | |\n\n## Facts side by side\n\n| Fact | Azure Maps | Radar |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft Azure | Radar Labs |\n| Hosted endpoint | `https://atlas.microsoft.com` | `https://api.radar.io/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Paid |\n| Price for geocoding | $4.50 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT | Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-30 | 2026-09-14 |\n| Terms last updated | no date given | 2023-05-24 |\n| Privacy policy last updated | 2026-09-01 | 2025-05-13 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 9.1k npm/wk, 25k PyPI/wk | none |\n\n## Verdicts\n\n**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.\n\n**Radar.** Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.\n\n## Before you call either\n\n### Azure Maps\n\n1. 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.\n2. 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.\n3. Use Search 1.0 (`/search/poi/json`, `/search/nearby/json`, `/search/fuzzy/json`) for places. The 2026-01-01 version has no place search.\n4. Use `eu.atlas.microsoft.com` or `us.atlas.microsoft.com` to keep request data in that geography.\n5. 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.\n\n### Radar\n\n1. Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com\n2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons\n3. Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses\n4. Set `units=metric` on routing calls. The default is imperial, with distances in feet\n5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented\n6. Do not keep geocoding, autocomplete or place results for more than 30 days\n\n## Questions\n\n### Which is better for AI agents, Azure Maps or Radar?\n\nAzure Maps scores 67.9 (B) on agent readiness against Radar's 53.3 (D), and leads in 6 of 7 scored categories. Radar leads on maintenance \u0026 community.\n\n### Do Azure Maps and Radar need an API key?\n\nAzure Maps takes an API key or an OAuth sign-in. Radar needs an API key.\n\n### Can an agent call Azure Maps and Radar without installing anything?\n\nYes. Azure Maps has a hosted endpoint at https://atlas.microsoft.com and Radar at https://api.radar.io/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-maps-vs-radar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-maps-vs-radar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-maps\", \"b\": \"radar\"}`. From a terminal: `anchor compare azure-maps radar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-maps.json and https://www.anchorterminal.com/api/v1/tools/radar.json\n\n## Other comparisons with Azure Maps or Radar\n\n- [Amazon Location Service vs Azure Maps](https://www.anchorterminal.com/compare/amazon-location-vs-azure-maps.md)\n- [Amazon Location Service vs Radar](https://www.anchorterminal.com/compare/amazon-location-vs-radar.md)\n- [ArcGIS Location Platform vs Azure Maps](https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.md)\n- [ArcGIS Location Platform vs Radar](https://www.anchorterminal.com/compare/arcgis-vs-radar.md)\n- [Azure Maps vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-geoapify.md)\n- [Azure Maps vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/azure-maps-vs-google-maps-platform.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs LocationIQ](https://www.anchorterminal.com/compare/azure-maps-vs-locationiq.md)\n- [Azure Maps vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-mapbox.md)\n- [Azure Maps vs MapQuest](https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.md)\n- [Azure Maps vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/azure-maps-vs-opencage.md)\n- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)\n- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)\n- [Geoapify Location Platform + MCP vs Radar](https://www.anchorterminal.com/compare/geoapify-vs-radar.md)\n- [Google Maps Platform + Grounding Lite MCP vs Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [Mapbox APIs + MCP vs Radar](https://www.anchorterminal.com/compare/mapbox-vs-radar.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Azure Maps vs Radar", "url": "" } ], "description": "Azure Maps scores 67.9 (B) to Radar's 53.3 (D) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Azure Maps B 67.9", "Radar D 53.3", "scores" ], "h1": "Azure Maps vs Radar", "image": "https://www.anchorterminal.com/assets/og/compare-azure-maps-vs-radar.png", "path": "/compare/azure-maps-vs-radar", "published": "2026-10-01", "section": "tools", "title": "Azure Maps vs Radar for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-radar" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }