# ArcGIS Location Platform vs MapTiler Cloud (slim)

> ArcGIS Location Platform scores 66.1 (B) to MapTiler Cloud's 62.1 (B) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/arcgis-vs-maptiler.md (~4,950 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/arcgis-vs-maptiler.json · canonical https://www.anchorterminal.com/compare/arcgis-vs-maptiler
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ArcGIS Location Platform scores 66.1 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 3 of 7 scored categories. MapTiler Cloud leads on schema & documentation and transparency & trust. Both do geocoding.

- ArcGIS Location Platform: B 66.1, rank #380 of 1486 · https://www.anchorterminal.com/tools/arcgis.min.md
- MapTiler Cloud: B 62.1, rank #574 of 1486 · https://www.anchorterminal.com/tools/maptiler.min.md
- ArcGIS Location Platform, good for Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding. Ahead on Reliability, 70 against 43; Agent ergonomics, 78 against 70; Maintenance & community, 83 against 70. Also A hosted endpoint, with nothing to install.
- MapTiler Cloud, good for Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency. Ahead on Schema & documentation, 79 against 61; Transparency & trust, 80 against 69. Also Free to start without a card.

| Category | ArcGIS Location Platform | MapTiler Cloud |
| --- | --- | --- |
| Reliability (16%) | 70 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 61 | 79 |
| Agent ergonomics (13%) | 78 | 70 |
| Security & auth (14%) | 64 | 64 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 70 |
| Transparency & trust (7%) | 69 | 80 |

| Fact (where they differ) | ArcGIS Location Platform | MapTiler Cloud |
| --- | --- | --- |
| Vendor | Esri | MapTiler AG |
| Hosted endpoint | `https://geocode-api.arcgis.com` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Price for geocoding | $0.50 per 1,000 requests | not published |
| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | none |
| Tools exposed | 9 | none |
| llms.txt | no | yes |
| Last release | 2026-10-27 | 2026-10-02 |
| Terms last updated | not read yet | no date given |
| Privacy policy last updated | 2026-07-31 | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | 115k npm/wk |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Reliability, ArcGIS Location Platform +27: ArcGIS Location Platform 70 (Graded as a hosted service on the REST location services, which are generally available. Esri runs its own status page at status.location.arcgis.com with current status and an event history (20). The history is drawn by script, so we read the platform's RSS feed at /admin/api/rss/all.rss, titled ArcGIS Location Platform Services Status. The page's own "all services RSS feed" link (location_platform.rss) answered 404 on 2 November. On 2 November its newest entry is still an intermittent basemap tile slowdown on 16 June 2026, outside the 90 days to 2 November. A readable feed that posts incidents, with none touching the product in the window, is a clean record (30). The 8 October check gave 25 and held back 5 for the feed's unknown depth, which isn't a checklist value. No request rate limits with numbers were found in the geocoding, places or routing reference (0, per the 8 October check, not re-read on 2 November). No 429 or backoff guidance was found. The geocoding output page says only that a timeout after 60 seconds may be retried later (0). The SLA of 23 December 2025 commits to 99.9 per cent monthly uptime for ten services (10). The REST services are generally available, and the MCP server is a beta (10). Total 70.); MapTiler Cloud 43 (Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43.)
- Schema & documentation, MapTiler Cloud +18: ArcGIS Location Platform 61 (No OpenAPI description was found for geocoding, places or routing. The geocoding service description at `GeocodeServer?f=pjson` lists each parameter with its type, allowed values and supported operations, which earns 8 of 25. `/llms.txt` returns 404 on developers.arcgis.com and location.arcgis.com (0). The reference explains when to use a direct request or a job, and stored or unstored geocoding (16 of 20). Parameters carry types, defaults, allowed values and maximums, such as `maxLocations` up to 50 and `pageSize` up to 20 (12 of 15). Each operation has request and response examples, and the geocoding output page lists error codes with extended codes and causes (13 of 15). Geocoding has dated release notes back to 2023 and the platform has release notes by month, but the geocoding path carries no version while places uses `/v1` (12 of 15). Total 61.); MapTiler Cloud 79 (OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79.)
- Maintenance & community, ArcGIS Location Platform +13: ArcGIS Location Platform 83 (The latest dated change is MCP server 1.0.0-beta.1.9 on 27 October 2026, which added stored and unstored geocoding and a service area tool (30). Dated entries in the 90 days to 2 November include MCP releases on 10 August, 1, 15 and 29 September, 9 and 27 October, the September 2026 platform and geocoding release notes, ArcGIS REST JS 4.11.0 on 7 August and 4.11.1 on 12 August, and the ArcGIS API for Python tag v2.4.4 on 22 September (20). Public release notes and the Esri Community forum exist, technical support is a paid extra, and we didn't read reply times. The 8 October check counted 60 open issues on the ArcGIS REST JS repository; github.com pages weren't readable on 2 November, and the clone's main branch was last changed on 7 August 2026 (10 of 15). Official SDKs are current, ArcGIS REST JS 4.11.1 and the ArcGIS API for Python 2.4.4 (15). The JS repository has pull-request test and release workflows, and we didn't check that they pass (8 of 10). Total 83.); MapTiler Cloud 70 (@maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70.)
- Transparency & trust, MapTiler Cloud +11: ArcGIS Location Platform 69 (A closed service with a dated agreement that states what may be stored, cached and shared, and an Apache-2.0 client library (15 of 30). The privacy statement was revised on 31 July 2026, the Products & Services supplement on 9 September 2025 and the Data Processing Addendum on 12 March 2024. None states a retention period, and neither the supplement nor the addendum names ArcGIS Location Platform (14 of 30). The agreement promises 90 days' notice for deprecations, and the July 2026 release notes record the retirement of legacy API keys (16 of 20). The addendum names four sub-processors as examples and the GDPR page says information is stored in the United States, with no list specific to this product (9 of 20). Total 54.); MapTiler Cloud 80 (Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64.)
- Agent ergonomics, ArcGIS Location Platform +8: ArcGIS Location Platform 78 (Responses can be sized with `outFields` and `maxLocations` on geocoding and `pageSize` on places (20 of 25). Places pages with `pageSize` and `offset` and filters by category and text, and geocoding filters by extent, country and category (18 of 20). Errors are a JSON object with `code`, `message` and `details`, with documented causes for 400, 403, 498 and 499 (15 of 20). The geocoding, places and routing calls are reads, so retries are safe, but no retry guidance was found and we didn't read the MCP tools' annotations (10 of 20). A geocode needs `f`, a token and an address, and Esri publishes ArcGIS REST JS and the ArcGIS API for Python (15). Total 78.); MapTiler Cloud 70 (API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.)