# Say what is at a set of coordinates

> Say what is at a set of coordinates: 5 companies fully do it, 13 with a limit, 18 carry the tag. Every listing in Maps, geocoding & places with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/maps.coordinates-to-address/
- Markdown: https://www.anchorterminal.com/niches/maps.coordinates-to-address/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/maps.coordinates-to-address/index.min.md (~430 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/maps.coordinates-to-address/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 5 | 13 | 18 | 16 | 10 |

## What counts as done

A structured address with country code, admin areas and postcode that contain the point, in the requested language, with the field set stable between versions; a point in a disputed region still gets a documented country answer.

Measured, for our own tests: the returned locality contains the point for at least 95 per cent of a test set across five countries.

How agents ask for it: what address is this GPS point; which city and country is this photo from; name these pins; what's the postcode here

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Amazon Location Service (Amazon Web Services, Inc.)**: ReverseGeocode returns a structured address with country, region, locality and PostalCodeDetails, takes Language, and a PoliticalView parameter documents how disputed areas are answered.
- **Azure Maps (Microsoft Corporation)**: GET /reverseGeocode returns the same structured address schema with resultTypes filtering, and a view parameter documents how disputed borders and labels are answered.
- **HERE Location Services (HERE Europe B.V.)**: Reverse geocoding shares the address schema with country code, state, county, city and postal code, takes BCP 47 lang, and a politicalView parameter sets the answer for disputed areas.
- **Mapbox APIs + MCP (Mapbox, Inc.)**: Reverse geocoding v6 returns a context object with country code, region, postcode and place, takes language, and worldview documents answers for disputed areas.
- **OpenCage Geocoding API (OpenCage GmbH)**: Reverse geocoding on the same endpoint returns components with ISO 3166-1 and 3166-2 codes, city, state and postcode in the requested language, and the docs explain how disputed and shared-postal areas are coded.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **ArcGIS Location Platform (Environmental Systems Research Institute, Inc.)**: Reverse geocoding is part of the Geocoding service with langCode and countryCode fields, but the reverseGeocode reference was not read, so admin fields and disputed-territory handling are unconfirmed.
- **Geoapify Location Platform + MCP (KEPTAGO LTD)**: Reverse geocoding and a reverse batch API exist, with lang and the same address fields as forward results, but no documented answer for disputed territories was found.
- **Geocodio (Dotsquare LLC)**: Single and batch reverse geocoding return structured addresses with unit-level refinement, but only in six countries, UK reverse results may be kept only twelve months after the subscription ends, and there is no language parameter.
- **Google Maps Platform + Grounding Lite MCP (Google LLC or a regional Google entity, by billing country)**: Reverse geocoding returns address components with a language parameter, but first-hand reports found no country code for Crimea and Kashmir in Places results, and a reverse-geocoding bill large enough to replace it.
- **LocationIQ (Unwired Labs (India) Pvt Ltd)**: /reverse returns a structured address with country code and postcode, but no documented answer for disputed territories was found, and the free plan must drop cached results after 48 hours.
- **MapQuest (Mapquest Holdings LLC)**: /geocoding/v1/reverse exists in GET and POST and in batch, but language and disputed-territory handling were not documented on the pages read.
- **MapTiler Cloud (MapTiler AG)**: Reverse geocoding returns GeoJSON features with country_code and a context hierarchy and takes a language parameter, but no documented answer for disputed territories was found.
- **NextBillion.ai (NextBillion.ai Pte. Ltd.)**: A reverse geocode endpoint is documented, returning the same structured address, but its language options and disputed-territory handling were not read.
- **Nominatim (Nominatim project (osm-search))**: Reverse returns precisely one result with addressdetails and country_code at a chosen zoom level and takes accept-language, but disputed territories are undocumented and a report of intermittent blank answers on the public server was closed as not planned.
- **Radar (Radar Labs, Inc.)**: /v1/geocode/reverse returns the same structured address with countryCode and a language option, but disputed territories are not documented and results may be kept only 30 days.
- **Stadia Maps (Stadia Maps, Inc.)**: Reverse geocoding returns structured addresses with country and admin fields and a lang parameter, but a first-hand report found v2 sometimes omits the formatted address line that v1 returns.
- **TomTom Maps APIs + MCP (TomTom International BV)**: A Reverse Geocoding API returns addresses or place names, but its reference, language handling and disputed-territory answers were not read; the view parameter appears on search calls.
- **Woosmap (WOOSMAP SAS)**: The same endpoint reverse geocodes a latlng into address components in the requested language, but only part of the components are translated and disputed territories are not documented.

## What stops agents finishing

- no country code for disputed territories
- field such as the formatted address missing on some results
- per-call price makes coarse country or state lookups costly at volume

## Around it

Before: photos.read-exif, personal-assistants.device-location. After: weather.forecast-for-place, data.write-rows, maps.find-places-nearby.

## Where this comes from

Weight 16 of 100 in Maps, geocoding & places: 10 of 53 accounts (wrong village or PIN code, missing country code, blank results, cost)

As data: https://www.anchorterminal.com/api/v1/use-cases/maps.coordinates-to-address.json, or the MCP tool get_use_case with id maps.coordinates-to-address. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
