{ "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": 259, "ranked": true, "rankOf": 722, "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-08T21:12:04.262139857Z", "lastOk": true, "lastStatus": 200, "lastMs": 145, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 138, "p95ms24h": 386, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.location.arcgis.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:14.482657019Z" }, "updatedAt": "2026-10-08T21:12:04.262139857Z" } }, "answer": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation.", "b": { "slug": "tomtom", "name": "TomTom Maps APIs + MCP", "vendor": "TomTom", "vendorUrl": "https://developer.tomtom.com", "kind": "http-api", "category": "maps", "summary": "Search, Geocoding and Reverse Geocoding, Routing, Matrix Routing, Reachable Range, EV routing and live traffic, plus map tiles.", "url": "https://www.anchorterminal.com/tools/tomtom", "markdownUrl": "https://www.anchorterminal.com/tools/tomtom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomtom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomtom.json", "repo": "https://github.com/tomtom-international/tomtom-mcp", "license": "Apache-2.0 (MCP server)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.tomtom.com", "packages": [ { "registry": "npm", "name": "@tomtom-org/tomtom-mcp" } ], "auth": "api-key", "authNotes": "One API key, passed as the key query parameter on REST calls. The hosted MCP takes it in a tomtom-api-key header and defaults to the Orbis backend. The local server defaults to the older TomTom Maps backend unless MAPS=tomtom-orbis-maps is set. Unreleased changes merged on 30 September 2026 drop the older backend, the tomtom-maps-backend header and the MAPS variable.", "pricing": "freemium", "pricingNotes": "Free monthly allowance with no card. 2,500 Search, 20,000 Geocoding, 20,000 Routing, 2,500 Matrix Routing, 200,000 vector and 200,000 raster tiles and 20,000 non-tile map requests. Past that it's pay as you grow in euros at volume tiers, worked out by an estimator on the pricing page. The per-request rates sit behind per-API detail links we couldn't read, so no rate is quoted here (https://docs.tomtom.com/pricing).", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": 55, "npmWeekly": 996, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.tomtom.com", "llmsTxt": "https://docs.tomtom.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "typescript", "free-tier", "no-card", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 54.9, "grade": "C", "agentReady": false, "rank": 524, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-01" }, "negative": 0, "verdict": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.", "bestFor": "Drive planning with live traffic, EV charging and reachable range.", "strengths": [ "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month", "Live traffic, EV routing and search, reachable range and search along a route as MCP tools", "All 18 MCP tools annotated read-only, idempotent and non-destructive", "Five MCP releases between 14 July and 23 September 2026, with Veracode scanning and end-to-end tests in CI", "HackerOne disclosure programme with a 3 business day first response" ], "weaknesses": [ "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified", "Status page keeps only five days of history", "Paid prices only through a euro estimator", "Hosted MCP in public preview and missing from the MCP registry", "Only 2,500 free Search and Matrix calls a month" ], "agentNotes": [ "Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address", "Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default", "Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal", "Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map", "Redact the key parameter before logging REST URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 30, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 74 }, "connect": { "http": "curl \"https://api.tomtom.com/search/2/geocode/10%20Downing%20Street%2C%20London.json?limit=1\u0026key=$TOMTOM_API_KEY\"", "claudeCode": "claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header \"tomtom-api-key: $TOMTOM_API_KEY\"", "config": { "mcpServers": { "tomtom": { "args": [ "-y", "@tomtom-org/tomtom-mcp@latest" ], "command": "npx", "env": { "TOMTOM_API_KEY": "${TOMTOM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/tomtom" }, "area": "everyday", "provenance": { "legalEntity": "TomTom International BV", "domain": "tomtom.com", "domainRegistered": "1996-02-23", "endpointOnVendorDomain": true, "terms": "https://docs.tomtom.com/legal/terms-and-conditions", "privacy": "https://www.tomtom.com/privacy/", "statusPage": "https://tomtom.service-now.com/status", "changelog": "", "securityTxt": "none", "checked": "2026-10-02", "notes": [ "The privacy policy names TomTom International BV and was last edited 1 August 2024. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.", "The terms page renders client-side and returned no readable text to our fetcher on 30 September, 1 October or 2 October, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified.", "www.tomtom.com/.well-known/security.txt returns 404. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.", "The status page shows current status per API and only the last five days of history.", "A deprecation policy page is linked from docs.tomtom.com/llms.txt but renders client-side, and its .md twin returns 404." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-10-08T21:12:23.763083861Z", "lastOk": true, "lastStatus": 200, "lastMs": 141, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 402, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:16.776326806Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.11", "released": "2026-10-05", "seenAt": "2026-10-08T16:32:33.085009115Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.11", "seenAt": "2026-10-08T16:32:32.173474546Z" } ], "githubStars": 56, "npmWeekly": 633, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:02.112536049Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:56.781511967Z" }, "domain": { "domain": "tomtom.com", "registered": "1996-02-23", "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com", "checkedAt": "2026-10-04T13:05:44.956685546Z" }, "pages": [ { "url": "https://docs.tomtom.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:19:40.589393441Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:01.446679763Z", "changedAt": "2026-10-08T18:31:01.446679763Z", "fingerprint": "b77d548785dc" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:19:38.500477859Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "updatedAt": "2026-10-08T21:12:23.763083861Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Esri", "b": "TomTom", "name": "Vendor" }, { "a": "https://geocode-api.arcgis.com", "b": "https://api.tomtom.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$0.50 per 1,000 requests", "b": "not published", "name": "Price for geo geocode" }, { "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": "Apache-2.0 (MCP server)", "name": "Licence" }, { "a": "8", "b": "15", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-29", "b": "2026-09-23", "name": "Last release" }, { "a": "", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-07-31", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "392 stars, 65k npm/wk, 33k PyPI/wk", "b": "55 stars, 996 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation.", "question": "Which is better for AI agents, ArcGIS Location Platform or TomTom Maps APIs + MCP?" }, { "answer": "ArcGIS Location Platform takes an API key or an OAuth sign-in. TomTom Maps APIs + MCP needs an API key.", "question": "Do ArcGIS Location Platform and TomTom Maps APIs + MCP need an API key?" }, { "answer": "Yes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and TomTom Maps APIs + MCP at https://api.tomtom.com.", "question": "Can an agent call ArcGIS Location Platform and TomTom Maps APIs + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 65 against 30", "Security \u0026 auth, 64 against 51", "Payments \u0026 pricing, 40 against 25", "Transparency \u0026 trust, 72 against 58" ], "also": null, "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, 71 against 61" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Drive planning with live traffic, EV charging and reachable range.", "slug": "tomtom", "watchFor": "Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified" } ], "job": { "capability": "geo.geocode", "name": "Geo geocode" }, "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-tomtom.json", "title": "Amazon Location Service vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, { "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-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/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-tomtom.json", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.json", "title": "Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom.json", "title": "LocationIQ vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom.json", "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" } ], "scores": [ { "arcgis": 65, "by": 35, "edge": "arcgis", "key": "reliability", "name": "Reliability", "tomtom": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "arcgis": 61, "by": 10, "edge": "tomtom", "key": "schema", "name": "Schema \u0026 documentation", "tomtom": 71, "weight": 13 }, { "arcgis": 78, "by": 0, "edge": "", "key": "ergonomics", "name": "Agent ergonomics", "tomtom": 78, "weight": 13 }, { "arcgis": 64, "by": 13, "edge": "arcgis", "key": "security", "name": "Security \u0026 auth", "tomtom": 51, "weight": 14 }, { "arcgis": 40, "by": 15, "edge": "arcgis", "key": "payments", "name": "Payments \u0026 pricing", "tomtom": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "arcgis": 83, "by": 3, "edge": "tomtom", "key": "maintenance", "name": "Maintenance \u0026 community", "tomtom": 86, "weight": 7 }, { "arcgis": 72, "by": 14, "edge": "arcgis", "key": "transparency", "name": "Transparency \u0026 trust", "tomtom": 58, "weight": 7 } ], "summary": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation. Both do geo geocode.", "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.", "tomtom": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom", "json": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md", "slim": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.min.md" }, "markdown": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation. Both do geo geocode.\n\n- ArcGIS Location Platform: grade B, 65.4/100, rank #259 of 722. Markdown https://www.anchorterminal.com/tools/arcgis.md · JSON https://www.anchorterminal.com/api/v1/tools/arcgis.json\n- TomTom Maps APIs + MCP: grade C, 54.9/100, rank #524 of 722. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.json\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 30\n- Security \u0026 auth, 64 against 51\n- Payments \u0026 pricing, 40 against 25\n- Transparency \u0026 trust, 72 against 58\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### TomTom Maps APIs + MCP (C)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 61\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified\n\n\n## Score by category\n\n| Category | Weight | ArcGIS Location Platform | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 30 | ArcGIS Location Platform +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 71 | TomTom Maps APIs + MCP +10 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 78 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 51 | ArcGIS Location Platform +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 25 | ArcGIS Location Platform +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 86 | TomTom Maps APIs + MCP +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 58 | ArcGIS Location Platform +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.4 · B** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | ArcGIS Location Platform | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Esri | TomTom |\n| Hosted endpoint | `https://geocode-api.arcgis.com` | `https://api.tomtom.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| Price for geo geocode | $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 | Apache-2.0 (MCP server) |\n| Tools exposed | 8 | 15 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-09-29 | 2026-09-23 |\n| Terms last updated | | couldn't be read |\n| Privacy policy last updated | 2026-07-31 | couldn't be read |\n| Customer content may train models | | couldn't be read |\n| Terms restrict automated access | | couldn't be read |\n| Terms restrict benchmarking | | couldn't be read |\n| Terms or service can change without notice | | couldn't be read |\n| Arbitration or class-action waiver | | couldn't be read |\n| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/5 (2) |\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**TomTom Maps APIs + MCP.** No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.\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### TomTom Maps APIs + MCP\n\n1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address\n2. Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default\n3. Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal\n4. Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map\n5. Redact the key parameter before logging REST URLs\n\n## Questions\n\n### Which is better for AI agents, ArcGIS Location Platform or TomTom Maps APIs + MCP?\n\nArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation.\n\n### Do ArcGIS Location Platform and TomTom Maps APIs + MCP need an API key?\n\nArcGIS Location Platform takes an API key or an OAuth sign-in. TomTom Maps APIs + MCP needs an API key.\n\n### Can an agent call ArcGIS Location Platform and TomTom Maps APIs + MCP without installing anything?\n\nYes. ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com and TomTom Maps APIs + MCP at https://api.tomtom.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/arcgis-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"arcgis\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare arcgis tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/arcgis.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with ArcGIS Location Platform or TomTom Maps APIs + MCP\n\n- [Amazon Location Service vs ArcGIS Location Platform](https://www.anchorterminal.com/compare/amazon-location-vs-arcgis.md)\n- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.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 Stadia Maps](https://www.anchorterminal.com/compare/arcgis-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 TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "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 TomTom Maps APIs + MCP", "url": "" } ], "description": "ArcGIS Location Platform scores 65.4 (B) on agent readiness against TomTom Maps APIs + MCP's 54.9 (C), and leads in 4 of 7 scored categories. TomTom Maps APIs + MCP leads on schema \u0026 documentation. Both do geo geocode. Category scores, facts, verdicts and agent notes side by…", "facts": [ "ArcGIS Location Platform B 65.4", "TomTom Maps APIs + MCP C 54.9", "scores" ], "h1": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-arcgis-vs-tomtom.png", "path": "/compare/arcgis-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }