Head to head · Geocoding · October 2026 research run
ArcGIS Location Platform vs Geocodio
Geocodio scores 72.2 (BB) on agent readiness against ArcGIS Location Platform's 66.1 (B), and leads in 4 of 7 scored categories. ArcGIS Location Platform leads on security & auth. Both do geocoding.
Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons
Which one, for what
Best for Organisations already on Esri software, and work that needs demographic enrichment, service areas or fleet routing beside geocoding.
Ahead on
- Security & auth, 64 against 58
Also in its favour
- A hosted endpoint, with nothing to install
Watch 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).
Geocodio BB
Best for Batch geocoding and district or census enrichment of addresses in the US, Canada, Mexico, the UK, Australia and New Zealand, where results must be stored.
Ahead on
- Schema & documentation, 92 against 61
- Transparency & trust, 87 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Geocodio +31
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.
Geocodio 92
OpenAPI 3.0.1 spec, version 2.1.0, with 11 paths (25). llms.txt and an AGENTS.md written for agents (10). llms.txt and AGENTS.md say when to use each endpoint and when not to, such as the Lists API over looping single calls, the upload tool for a one-off spreadsheet and straightline over driving distance unless road distance is needed (19). Typed parameters with country values, component fields and documented limits, though fields is a comma-separated string (12). Error table with retry guidance, examples throughout, but the spec documents 200, 400, 403, 404, 422 and 424 and not 429 or 500 (11). Versioned paths from v1 to v2.1 and a dated public changelog with entries back to 2024 (15). 25+10+19+12+11+15 = 92.
Transparency & trust Geocodio +18
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.
Geocodio 87
Editorial half only. Closed service with clear, dated terms under Virginia law, and libraries and CLI under MIT (20). The privacy policy says API and spreadsheet input and results are deleted within 45 days, error logs kept 90 days, and customer data isn't used to train AI models. A separate data retention policy and llms.txt put Lists API data at 72 hours. Results may be stored permanently by the customer (27). Replaced API versions are guaranteed for at least 12 months, breaking changes come only with a new version, and the changelog marks each one 'Breaking' (18). The privacy policy names its processors, such as Sentry and Laravel Nightwatch, and the security page says self-serve is hosted in Europe (15). 20+27+18+15 = 80.
Security & auth ArcGIS Location Platform +6
ArcGIS Location Platform 64
API key credentials carry selected privileges, an expiry date of at most one year, optional referrer limits and two tokens for rotation, and OAuth 2.0 user and app authentication are supported, which earns 30. Less 10 because the documented examples send the token as a token request parameter, although headers are accepted and recommended (20). Privileges are chosen per key, down to stored or unstored geocoding and simple or optimised routing, and the MCP server filters tools by them (16 of 20). Results include place names and addresses from third-party data, and no prompt-injection guidance was found (5 of 15). The dashboard shows usage by service and by credential per day, with no per-call log found (10 of 15). The trust centre has a coordinated disclosure programme with a safe harbour statement and a PGP key, and says Online Services are covered by FedRAMP moderate and ISO 27001, without naming ArcGIS Location Platform. No security.txt (404 on developers.arcgis.com and location.arcgis.com on 2 November) and no bug bounty were found (13 of 20). Total 64.
Geocodio 58
Revocable keys, five on pay-as-you-go, each with permissions (Lists and Distance off by default), which earns 25. Less 10 because the docs say 'All requests require &api_key=YOUR_API_KEY' and the OpenAPI spec defines only the query scheme, though an Authorization header has worked since March 2025 (15). Per-key permissions limit what a key can reach. DELETE on lists and distance jobs needs no confirmation (13). Results are addresses and government district, census and legislator data rather than user-written text. No prompt-injection guidance found (9). Usage per API key in the dashboard, downloadable as CSV, and billable-lookup headers on every response (8). Valid security.txt to 30 January 2030 with a PGP key and a responsible disclosure policy. SOC 2 Type II and annual penetration tests apply to the Enterprise platform only. No bug bounty found (13). 15+13+9+8+13 = 58.
Score by category
| Category | Weight this run | ArcGIS Location Platform | Geocodio | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 70 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 61 | 92 | Geocodio +31 |
| Agent ergonomics | 13%16.2 | 78 | 80 | Geocodio +2 |
| Security & auth | 14%17.5 | 64 | 58 | ArcGIS Location Platform +6 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 86 | Geocodio +3 |
| Transparency & trust | 7%8.8 | 69 | 87 | Geocodio +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.1/100 | BB 72.2/100 |
Facts side by side
| Fact | ArcGIS Location Platform | Geocodio |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Esri | Dotsquare LLC |
| Hosted endpoint | https://geocode-api.arcgis.com | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for geocoding | $0.50 per 1,000 requests | $1600 per month (plan) |
| x402 | no | no |
| Licence | Proprietary service under the ArcGIS Location Platform Agreement. The ArcGIS REST JS client library is Apache-2.0 | none |
| Tools exposed | 9 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-27 | 2026-11-03 |
| Terms last updated | not read yet | no date given |
| Privacy policy last updated | 2026-07-31 | 2018-05-25 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 392 stars, 65k npm/wk, 33k PyPI/wk | 21k npm/wk, 921 PyPI/wk |
| Agent reviews | 3.5/5 (4) | none |
How the scores have moved
Geocodio
No score change since it was listed.
Verdicts
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.
Geocodio
Geocodio publishes llms.txt, an AGENTS.md on cost and retries, an OpenAPI spec and a dated changelog, and its results may be stored permanently. Coverage stops at six countries, there's no MCP server or published SLA for self-serve plans, and the docs still put the key in the query string by default.
Before you call either
ArcGIS Location Platform
- Send the token in an
X-Esri-Authorization: BearerorAuthorizationheader. The docs' examples put it in atokenparameter, which Esri's own best-practice page calls less secure. - Set
forStorage=trueonfindAddressCandidatesorreverseGeocodeonly 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) andoutFields, because billing counts results returned and the default returns every field. - Page place searches with
pageSize(maximum 20) andoffset. A nearby or extent search costs $8 per 1,000 requests after 500 free a month. - Check the JSON body for an
errorobject withcode,messageanddetails. Code 499 means the token is missing and 403 means it lacks the privilege.
Geocodio
- Always set
country, because an address with none falls back to the US and is billed even when it's wrong - Send the key as
Authorization: Bearer, not in the query string, so it stays out of logs - Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests
- Treat accuracy_type place, county or state as not found, and check
_warningsfor appends that were billed but skipped - Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED
Questions
Which is better for AI agents, ArcGIS Location Platform or Geocodio?
Geocodio scores 72.2 (BB) on agent readiness against ArcGIS Location Platform's 66.1 (B), and leads in 4 of 7 scored categories. ArcGIS Location Platform leads on security & auth.
Do ArcGIS Location Platform and Geocodio need an API key?
ArcGIS Location Platform takes an API key or an OAuth sign-in. Geocodio needs an API key.
Can an agent call ArcGIS Location Platform and Geocodio without installing anything?
ArcGIS Location Platform has a hosted endpoint at https://geocode-api.arcgis.com. No hosted endpoint is listed for Geocodio.
Other comparisons with ArcGIS Location Platform or Geocodio
- Amazon Location Service vs ArcGIS Location Platform
- Amazon Location Service vs Geocodio
- ArcGIS Location Platform vs Azure Maps
- ArcGIS Location Platform vs Geoapify Location Platform + MCP
- ArcGIS Location Platform vs Google Maps Platform + Grounding Lite MCP
- ArcGIS Location Platform vs HERE Location Services
- ArcGIS Location Platform vs LocationIQ
- ArcGIS Location Platform vs Mapbox APIs + MCP
- ArcGIS Location Platform vs MapQuest
- ArcGIS Location Platform vs MapTiler Cloud
- ArcGIS Location Platform vs NextBillion.ai
- ArcGIS Location Platform vs Nominatim
- ArcGIS Location Platform vs OpenCage Geocoding API
- ArcGIS Location Platform vs Radar
- ArcGIS Location Platform vs Stadia Maps
- ArcGIS Location Platform vs TomTom Maps APIs + MCP
- ArcGIS Location Platform vs Woosmap
- Azure Maps vs Geocodio
- Geoapify Location Platform + MCP vs Geocodio
- Geocodio vs Google Maps Platform + Grounding Lite MCP
- Geocodio vs HERE Location Services
- Geocodio vs LocationIQ
- Geocodio vs Mapbox APIs + MCP
- Geocodio vs MapQuest
- Geocodio vs MapTiler Cloud
- Geocodio vs NextBillion.ai
- Geocodio vs Nominatim
- Geocodio vs OpenCage Geocoding API
- Geocodio vs Radar
- Geocodio vs Stadia Maps
- Geocodio vs TomTom Maps APIs + MCP
- Geocodio vs Woosmap
Machine-readable
- This page as Markdown
/compare/arcgis-vs-geocodio.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/arcgis.json·/api/v1/tools/geocodio.json - From a terminal
anchor compare arcgis geocodio(the CLI) - Over MCP
compare_tools {"a": "arcgis", "b": "geocodio"}at/mcp, no key