{ "data": { "a": { "slug": "arcgis", "name": "ArcGIS Location Platform", "vendor": "Esri", "vendorUrl": "https://location.arcgis.com", "kind": "http-api", "category": "maps", "summary": "Esri's pay-as-you-go location services for developers. REST APIs cover geocoding, reverse and batch geocoding, place search, routing, basemap tiles, static maps, elevation and demographic enrichment, with an Esri-hosted MCP server in beta.", "url": "https://www.anchorterminal.com/tools/arcgis", "markdownUrl": "https://www.anchorterminal.com/tools/arcgis.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/arcgis.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/arcgis.json", "repo": "https://github.com/Esri/arcgis-rest-js", "license": "Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://geocode-api.arcgis.com", "packages": [ { "registry": "npm", "name": "@esri/arcgis-rest-geocoding" }, { "registry": "npm", "name": "@esri/arcgis-rest-request" }, { "registry": "pypi", "name": "arcgis" } ], "auth": "mixed", "authNotes": "Self-serve. A free ArcGIS Location Platform account created in a browser issues API key credentials with selected privileges, an expiry date of up to one year, optional referrer limits and two tokens for rotation. OAuth 2.0 user authentication and app authentication (client ID and secret, short-lived tokens) are also supported. Requests take the token as a `token` parameter or in an `X-Esri-Authorization` or `Authorization` header. Accounts are for one person and may not be shared.", "pricing": "freemium", "pricingNotes": "Usage-based in US dollars with a monthly free tier and no contract. Free each month are 20,000 unstored geocodes, 20,000 routes, 500 place searches, 2 million basemap tiles, 1,000 static maps and 50,000 elevation points. A payment method (card, purchase order or voucher) is needed only to turn on pay-as-you-go, which services without a free tier, among them stored geocodes, require. The sign-up form is drawn by script and we couldn't read whether it asks for a card.", "priceSummary": "$0.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the billing help or the REST and MCP documentation (checked 2026-10-08).", "endpoints": [] }, "toolCount": 8, "popularity": { "githubStars": 392, "npmWeekly": 65286, "pypiWeekly": 32974, "asOf": "2026-10-08" }, "docsUrl": "https://developers.arcgis.com/rest/location-based-services/", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "maps", "geocoding", "routing", "places", "api-key", "oauth", "mcp", "beta-mcp", "free-tier", "usage-priced", "sla", "status-page", "typescript", "python" ], "lastRelease": "2026-09-29", "graded": true, "anchor": { "graded": true, "score": 65.4, "grade": "B", "agentReady": false, "rank": 320, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 83, "payments": 40, "reliability": 65, "schema": 61, "security": 64, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.", "strengths": [ "Every service has a public unit price and most have a monthly free tier, such as 20,000 geocodes, 20,000 routes and 2 million basemap tiles (https://location.arcgis.com/pricing/).", "API key credentials carry selected privileges, an expiry date of up to one year, optional referrer limits and two tokens for rotation. OAuth 2.0 user and app authentication are also supported.", "A published SLA commits to 99.9 per cent monthly uptime for ten services, with credits of 10 or 20 per cent of the monthly bill for the affected service (document G632a, 23 December 2025).", "The agreement promises 90 days' notice for deprecations of SDKs, APIs and location services (ArcGIS Location Platform Agreement, revised 21 November 2025, section 4.1).", "An Esri-hosted MCP server at `https://location-services-mcp.arcgis.com/beta/mcp` has eight tools, filters them by the token's privileges and adds no charge on top of service rates." ], "weaknesses": [ "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).", "No request rate limits, 429 behaviour or retry guidance were found in the geocoding, places or routing reference pages we read.", "No OpenAPI description or llms.txt was found. `/llms.txt` returns 404 on developers.arcgis.com and location.arcgis.com.", "Storing a geocode needs `forStorage=true` at $4 per 1,000 with no free tier, against $0.50 per 1,000 for results that may not be kept. The MCP geocoding tools bill at the stored rate.", "The MCP server is a beta under an Early Access programme, and the SLA excludes beta, evaluation and free services. Technical support is sold separately." ], "agentNotes": [ "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.", "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.", "Cap geocoding output with `maxLocations` (default and maximum 50) and `outFields`, because billing counts results returned and the default returns every field.", "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.", "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." ], "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": 65.4 } ], "editorialScores": { "ergonomics": 78, "maintenance": 83, "payments": 40, "reliability": 65, "schema": 61, "security": 64, "transparency": 54 }, "provenanceScore": 89 }, "connect": { "install": "npm install @esri/arcgis-rest-request @esri/arcgis-rest-geocoding", "http": "curl https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates \\\n -d \"f=pjson\" \\\n -d \"address=1600 Pennsylvania Ave NW, DC\" \\\n -d \"token=\u003cACCESS_TOKEN\u003e\"", "config": { "servers": { "mcpArcGISLocationServices": { "headers": { "Authorization": "Bearer ${input:esriApiKey}" }, "type": "http", "url": "https://location-services-mcp.arcgis.com/beta/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/arcgis" }, "area": "everyday", "unitPrices": [ { "item": "Geocodes, not stored (after 20,000 free a month)", "unit": "1k-requests", "usd": 0.5 }, { "item": "Geocodes, stored (`forStorage=true`, no free tier)", "unit": "1k-requests", "usd": 4 }, { "item": "Places nearby and extent search (after 500 free a month)", "unit": "1k-requests", "usd": 8 }, { "item": "Routes (after 20,000 free a month)", "unit": "1k-requests", "usd": 0.5 }, { "item": "Routes, stop-optimised (no free tier)", "unit": "1k-requests", "usd": 50 }, { "item": "Service areas (after 5,000 free a month)", "unit": "1k-requests", "usd": 50 }, { "item": "Basemap tiles (after 2 million free a month)", "unit": "1k-requests", "usd": 0.15 }, { "item": "Static maps (after 1,000 free a month)", "unit": "1k-requests", "usd": 0.9 }, { "item": "Elevation, per 1,000 points (after 50,000 free a month)", "unit": "1k-requests", "usd": 1 } ], "provenance": { "legalEntity": "Environmental Systems Research Institute, Inc.", "domain": "arcgis.com", "domainRegistered": "1999-06-09", "endpointOnVendorDomain": true, "terms": "https://www.esri.com/content/dam/esrisites/en-us/media/legal/platform/platform-legal.pdf", "privacy": "https://www.esri.com/en-us/privacy/privacy-statements/privacy-statement", "statusPage": "https://status.location.arcgis.com", "changelog": "https://location.arcgis.com/help/release-notes/2026-07/", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The ArcGIS Location Platform Agreement (E204 Platform Legal, revised 21 November 2025) is between the customer and Environmental Systems Research Institute, Inc., a California corporation at 380 New York Street, Redlands, California 92373-8100.", "The privacy statement (revised 31 July 2026) is the one the product's pages link. Esri also publishes a Products \u0026 Services Privacy Statement Supplement (9 September 2025) and a Data Processing Addendum (12 March 2024). Neither names ArcGIS Location Platform. The agreement's section 11.5 points to the addendum.", "The services answer on arcgis.com subdomains, among them geocode-api.arcgis.com, places-api.arcgis.com and location-services-mcp.arcgis.com.", "`/.well-known/security.txt` returns 404 on www.esri.com, developers.arcgis.com, location.arcgis.com and www.arcgis.com. The trust centre takes reports through a form, with a PGP key and a safe harbour statement.", "RDAP gives 1999-06-09 for arcgis.com and 1990-04-18 for esri.com, both registered through MarkMonitor Inc.", "The status page is Esri's own. Its event history is drawn by script, so we read the RSS feed it links, whose newest entry is dated 16 June 2026." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/arcgis.json", "live": { "slug": "arcgis", "probe": { "target": "https://geocode-api.arcgis.com", "method": "get", "lastAt": "2026-10-10T02:54:46.50872534Z", "lastOk": true, "lastStatus": 200, "lastMs": 139, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 136, "p95ms24h": 297, "samples24h": 249, "samples30d": 330, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.location.arcgis.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:06.388512304Z" }, "versions": [ { "registry": "github", "name": "Esri/arcgis-rest-js", "version": "@esri/arcgis-rest-request@4.11.1", "released": "2026-08-12", "seenAt": "2026-10-09T16:40:10.63407408Z" }, { "registry": "npm", "name": "@esri/arcgis-rest-geocoding", "version": "4.11.0", "seenAt": "2026-10-09T16:40:08.067975698Z" }, { "registry": "npm", "name": "@esri/arcgis-rest-request", "version": "4.11.0", "seenAt": "2026-10-09T16:40:09.058359447Z" }, { "registry": "pypi", "name": "arcgis", "version": "2.4.3", "released": "2026-04-21", "seenAt": "2026-10-09T16:40:10.350279101Z" } ], "githubStars": 392, "npmWeekly": 7091, "pypiWeekly": 33537, "securityTxt": { "url": "https://arcgis.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:08.698287425Z" }, "pages": [ { "url": "https://location.arcgis.com/help/release-notes/2026-07/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:41:29.672428533Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "922636767359" }, { "url": "https://www.esri.com/en-us/privacy/privacy-statements/privacy-statement", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:49:56.361581956Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a1bf1873839c" } ], "updatedAt": "2026-10-10T02:54:46.50872534Z" } }, "answer": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation.", "b": { "slug": "here-location-services", "name": "HERE Location Services", "vendor": "HERE Technologies", "vendorUrl": "https://www.here.com", "kind": "http-api", "category": "maps", "summary": "HERE Technologies' REST APIs for geocoding, place search, routing, matrix and isoline routing, traffic, transit and map tiles, called with an API key or OAuth token. A hosted MCP server, HERE Location Reasoning, exposes 13 of these operations as tools.", "url": "https://www.anchorterminal.com/tools/here-location-services", "markdownUrl": "https://www.anchorterminal.com/tools/here-location-services.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/here-location-services.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/here-location-services.json", "license": "Proprietary service under the HERE Platform Terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://geocode.search.hereapi.com/v1", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A HERE platform account, created in a browser with email verification, lets a person register an app and create up to two API keys, OAuth 2.0 credentials or OAuth 2.1 `private_key_jwt` credentials. REST calls take the key as the `apiKey` query parameter or a bearer token from https://account.api.here.com/oauth2/token. Location Reasoning needs a bearer token on `tools/call` and an account entitlement, and returns 403 without one.", "pricing": "freemium", "pricingNotes": "HERE's docs say a new organisation can get started for free on the Base Plan. The price table at here.com/get-started/pricing is drawn by script and was not read, so no allowance or per-request price is quoted. Support plans run from $50 a month (Developer). Location Reasoning is also sold through AWS Marketplace (checked 2026-10-09).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.here.com", "llmsTxt": "https://docs.here.com/llms.txt", "openapi": "https://docs.here.com/geocoding-and-search/reference/get_geocode.md", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "openapi", "llms-txt", "oauth", "free-tier", "enterprise", "eu", "sla", "closed-source" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 58, "grade": "C", "agentReady": false, "rank": 591, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "10 July 2026. The Routing v8 changelog marks `mlDuration` as Deprecated and says `return=mlDuration` is still accepted but no longer returns a value. HERE's lifecycle policy says a deprecated feature continues to operate for 6 to 12 months after notice. Three points (https://docs.here.com/routing/docs/routing-v8-changelog.md)" ], "verdict": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.", "bestFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "strengths": [ "Every endpoint page has a Markdown twin holding its OpenAPI 3.0 definition, indexed from `llms.txt` files per product", "99.9 per cent monthly availability targets published for Geocoding and Search v7 and Routing v8", "Lifecycle policy promises six months' notice before a product is discontinued and 6 to 12 months for a deprecated feature", "OAuth 2.1 `private_key_jwt` credentials alongside API keys, with two keys an app for rotation and trusted-domain limits", "ISO 27001, 27701, 27017, 27018 and 42001 certificates, TISAX AL3, and SOC 2 Type 2 for Platform Foundation and Workspace" ], "weaknesses": [ "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run", "The Base Plan price table is drawn by script, so per-request prices, free allowances and rate limits were not read", "API keys travel in the `apiKey` query parameter", "Results may be cached or stored outside the platform for 30 days at most, and only as HTTP caching headers allow", "Location Reasoning returns 403 unless the account is entitled, and the docs send the reader to an account representative or AWS Marketplace", "The acceptable use policy of January 2022 lists benchmarking and scraping among prohibited activities" ], "agentNotes": [ "Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL", "Do not store results for more than 30 days, and follow the HTTP caching headers on each response", "Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota", "Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support", "For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58 } ], "editorialScores": { "ergonomics": 74, "maintenance": 60, "payments": 10, "reliability": 57, "schema": 87, "security": 65, "transparency": 52 }, "provenanceScore": 73 }, "connect": { "http": "curl \"https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston\u0026limit=4\u0026apiKey=$HERE_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/here-location-services" }, "area": "everyday", "provenance": { "legalEntity": "HERE Europe B.V.", "domain": "here.com", "domainRegistered": "1995-06-11", "endpointOnVendorDomain": false, "terms": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "privacy": "https://www.here.com/en-gb/privacy", "statusPage": "https://status.here.com/status", "changelog": "https://docs.here.com/routing/docs/routing-v8-changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The HERE Platform Terms, effective 18 September 2023, name HERE Europe B.V., Kennedyplein 222-226, 5611 ZT Eindhoven, as contracting party, and HERE North America, LLC, Chicago, for customers in the Americas.", "The privacy policy, effective 29 August 2024, names HERE Global B.V. as controller and says it does not apply to personal data processed on behalf of customers. The Platform Terms incorporate it and a Data Processing Agreement published as a PDF.", "The APIs answer on hereapi.com (for example geocode.search.hereapi.com and router.hereapi.com) and the MCP server on hlr.here.ai, both second domains of the vendor.", "www.here.com/.well-known/security.txt returned the site's error page. The security page gives security@here.com and a 90-day disclosure window.", "RDAP for here.com gives a registration date of 1995-06-11.", "legal.here.com/en-gb/terms/here-platform redirects to the September 2023 terms on www.here.com." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/here-location-services.json", "live": { "slug": "here-location-services", "probe": { "target": "https://geocode.search.hereapi.com/v1", "method": "get", "lastAt": "2026-10-10T02:54:57.537414358Z", "lastOk": true, "lastStatus": 404, "lastMs": 60, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 124, "samples24h": 115, "samples30d": 115, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.here.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:40.516930569Z" }, "pages": [ { "url": "https://docs.here.com/routing/docs/routing-v8-changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:28.07952108Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c940c6209b7e" }, { "url": "https://www.here.com/en-gb/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:50:53.049981302Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bbe0eed0a23e" }, { "url": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:50:55.117836401Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "466d77d5e000" } ], "updatedAt": "2026-10-10T02:54:57.537414358Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Esri", "b": "HERE Technologies", "name": "Vendor" }, { "a": "https://geocode-api.arcgis.com", "b": "https://geocode.search.hereapi.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$0.50 per 1,000 requests", "b": "not published", "name": "Price for geocoding" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0", "b": "Proprietary service under the HERE Platform Terms", "name": "Licence" }, { "a": "8", "b": "13", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-29", "b": "2026-09-09", "name": "Last release" }, { "a": "", "b": "2023-09-18", "name": "Terms last updated" }, { "a": "2026-07-31", "b": "2024-08-29", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "392 stars, 65k npm/wk, 33k PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation.", "question": "Which is better for AI agents, ArcGIS Location Platform or HERE Location Services?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do ArcGIS Location Platform and HERE Location Services need an API key?" }, { "answer": "Yes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and HERE Location Services at https://geocode.search.hereapi.com/v1.", "question": "Can an agent call ArcGIS Location Platform and HERE Location Services without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 65 against 57", "Payments \u0026 pricing, 40 against 10", "Maintenance \u0026 community, 83 against 60", "Transparency \u0026 trust, 72 against 63" ], "also": [ "No incidents deducted, where HERE Location Services loses 3 points for them" ], "goodFor": "Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.", "slug": "arcgis", "watchFor": "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)." }, { "aheadOn": [ "Schema \u0026 documentation, 87 against 61" ], "also": null, "goodFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "slug": "here-location-services", "watchFor": "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run" } ], "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.json", "title": "Amazon Location Service vs ArcGIS Location Platform", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-arcgis" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.json", "title": "Amazon Location Service vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services" }, { "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-geoapify.json", "title": "ArcGIS Location Platform vs Geoapify Location Platform + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geoapify" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform.json", "title": "ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-locationiq.json", "title": "ArcGIS Location Platform vs LocationIQ", "url": "https://www.anchorterminal.com/compare/arcgis-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-mapbox.json", "title": "ArcGIS Location Platform vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest.json", "title": "ArcGIS Location Platform vs MapQuest", "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-opencage.json", "title": "ArcGIS Location Platform vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/arcgis-vs-opencage" }, { "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/arcgis-vs-stadia-maps.json", "title": "ArcGIS Location Platform vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, { "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/geoapify-vs-here-location-services.json", "title": "Geoapify Location Platform + MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.json", "title": "Google Maps Platform + Grounding Lite MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json", "title": "HERE Location Services vs LocationIQ", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json", "title": "HERE Location Services vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json", "title": "HERE Location Services vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, { "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/here-location-services-vs-stadia-maps.json", "title": "HERE Location Services vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.json", "title": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" } ], "scores": [ { "arcgis": 65, "by": 8, "edge": "arcgis", "here-location-services": 57, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "arcgis": 61, "by": 26, "edge": "here-location-services", "here-location-services": 87, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "arcgis": 78, "by": 4, "edge": "arcgis", "here-location-services": 74, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "arcgis": 64, "by": 1, "edge": "here-location-services", "here-location-services": 65, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "arcgis": 40, "by": 30, "edge": "arcgis", "here-location-services": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "arcgis": 83, "by": 23, "edge": "arcgis", "here-location-services": 60, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "arcgis": 72, "by": 9, "edge": "arcgis", "here-location-services": 63, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation. Both do geocoding.", "verdicts": { "arcgis": "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.", "here-location-services": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services", "json": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md", "slim": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.min.md" }, "markdown": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation. Both do geocoding.\n\n- ArcGIS Location Platform: grade B, 65.4/100, rank #320 of 950. Markdown https://www.anchorterminal.com/tools/arcgis.md · JSON https://www.anchorterminal.com/api/v1/tools/arcgis.json\n- HERE Location Services: grade C, 58/100, rank #591 of 950. Markdown https://www.anchorterminal.com/tools/here-location-services.md · JSON https://www.anchorterminal.com/api/v1/tools/here-location-services.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### ArcGIS Location Platform (B)\n\nGood for: Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.\n\nAhead on:\n- Reliability, 65 against 57\n- Payments \u0026 pricing, 40 against 10\n- Maintenance \u0026 community, 83 against 60\n- Transparency \u0026 trust, 72 against 63\n\nAlso in its favour:\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch 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).\n\n### HERE Location Services (C)\n\nGood for: Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.\n\nAhead on:\n- Schema \u0026 documentation, 87 against 61\n\nWatch for: Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run\n\n\n## Score by category\n\n| Category | Weight | ArcGIS Location Platform | HERE Location Services | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 57 | ArcGIS Location Platform +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 87 | HERE Location Services +26 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 74 | ArcGIS Location Platform +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 65 | HERE Location Services +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 10 | ArcGIS Location Platform +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 60 | ArcGIS Location Platform +23 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 63 | ArcGIS Location Platform +9 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **65.4 · B** | **58 · C** | |\n\n## Facts side by side\n\n| Fact | ArcGIS Location Platform | HERE Location Services |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Esri | HERE Technologies |\n| Hosted endpoint | `https://geocode-api.arcgis.com` | `https://geocode.search.hereapi.com/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| Price for geocoding | $0.50 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | Proprietary service under the HERE Platform Terms |\n| Tools exposed | 8 | 13 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-29 | 2026-09-09 |\n| Terms last updated | | 2023-09-18 |\n| Privacy policy last updated | 2026-07-31 | 2024-08-29 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | yes |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | none |\n\n## Verdicts\n\n**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.\n\n**HERE Location Services.** Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.\n\n## Before you call either\n\n### ArcGIS Location Platform\n\n1. 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.\n2. 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.\n3. Cap geocoding output with `maxLocations` (default and maximum 50) and `outFields`, because billing counts results returned and the default returns every field.\n4. 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.\n5. 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.\n\n### HERE Location Services\n\n1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL\n2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response\n3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota\n4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support\n5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`\n\n## Questions\n\n### Which is better for AI agents, ArcGIS Location Platform or HERE Location Services?\n\nArcGIS Location Platform scores 65.4 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation.\n\n### Do ArcGIS Location Platform and HERE Location Services need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call ArcGIS Location Platform and HERE Location Services without installing anything?\n\nYes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and HERE Location Services at https://geocode.search.hereapi.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.json, and with the fewest tokens: https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"arcgis\", \"b\": \"here-location-services\"}`. From a terminal: `anchor compare arcgis here-location-services`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/arcgis.json and https://www.anchorterminal.com/api/v1/tools/here-location-services.json\n\n## Other comparisons with ArcGIS Location Platform or HERE Location Services\n\n- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [ArcGIS Location Platform vs Azure Maps](https://www.anchorterminal.com/compare/arcgis-vs-azure-maps.md)\n- [ArcGIS Location Platform vs Geoapify Location Platform + MCP](https://www.anchorterminal.com/compare/arcgis-vs-geoapify.md)\n- [ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/arcgis-vs-google-maps-platform.md)\n- [ArcGIS Location Platform vs LocationIQ](https://www.anchorterminal.com/compare/arcgis-vs-locationiq.md)\n- [ArcGIS Location Platform vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-mapbox.md)\n- [ArcGIS Location Platform vs MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)\n- [ArcGIS Location Platform vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/arcgis-vs-opencage.md)\n- [ArcGIS Location Platform vs Radar](https://www.anchorterminal.com/compare/arcgis-vs-radar.md)\n- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)\n- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md)\n- [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md)\n- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-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": "ArcGIS Location Platform vs HERE Location Services", "url": "" } ], "description": "ArcGIS Location Platform scores 65.4 (B) to HERE Location Services's 58 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ArcGIS Location Platform B 65.4", "HERE Location Services C 58", "scores" ], "h1": "ArcGIS Location Platform vs HERE Location Services", "image": "https://www.anchorterminal.com/assets/og/compare-arcgis-vs-here-location-services.png", "path": "/compare/arcgis-vs-here-location-services", "published": "2026-10-01", "section": "tools", "title": "ArcGIS Location Platform vs HERE Location Services (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services" }, "tokens": { "markdown": 2750, "slim": 730 }, "version": 1 }