Niches · Maps, geocoding & places
Turn one address or place name into coordinates
Four or more companies' docs show a full fit.
What counts as done
One best match with coordinates, a normalised address, the country and a precision or match level (rooftop, street, postcode, locality), so the agent can reject a city-centre fallback; no match is reported as no match rather than a distant guess.
Measured, for our own tests: the best match falls within 100 m of known coordinates for street addresses in each test country, in one call. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: where is this address
, geocode 10 Downing Street
, get the coordinates for this venue
, what's the bounding box for the Bay Area
Does the job 11
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Amazon Location Service A Amazon Web Services, Inc. | Geocode returns Position, a structured Address with country, PlaceType (PointAddress, InterpolatedAddress, Street, Locality, PostalCode and more) and per-component MatchScores to threshold on; per-country Point Address coverage is published. source |
| ArcGIS Location Platform B Environmental Systems Research Institute, Inc. | findAddressCandidates returns candidates with a score and Addr_type (PointAddress, PointAddressInt, StreetAddress, Postal, Locality), takes countryCode, postal and postalExt, langCode, and locationType for rooftop or street entrance. source |
| Azure Maps B Microsoft Corporation | GET /geocode (2026-01-01) returns GeoJSON features with a structured address (countryRegion, adminDistricts, postalCode), an entity type, confidence and matchCodes to threshold on, and takes countryRegion and structured fields. source |
| Google Maps Platform + Grounding Lite MCP BB Google LLC or a regional Google entity, by billing country | Geocoding returns address components, formatted address, location_type (ROOFTOP, RANGE_INTERPOLATED, GEOMETRIC_CENTER, APPROXIMATE), partial_match, and ZERO_RESULTS when nothing matches. source |
| HERE Location Services C HERE Europe B.V. | /geocode returns resultType (houseNumber, street, locality, administrativeArea and more), houseNumberType for point or interpolated addresses, and scoring per field; a first-hand benchmark had HERE six points ahead of Google on 500 US addresses. source |
| Mapbox APIs + MCP A Mapbox, Inc. | Geocoding v6 returns coordinates with accuracy (rooftop and others), feature type, place_formatted, country context and a match_code with per-component status and a confidence value; worldview handles disputed areas. source |
| NextBillion.ai C NextBillion.ai Pte. Ltd. | Forward geocode returns items with alpha-3 countryCode, houseNumber and other address parts, a resultType and scoring.queryScore out of 1 to threshold on, with in=countryCode filters. source |
| OpenCage Geocoding API B OpenCage GmbH | One endpoint returns geometry, formatted address, ISO 3166 country codes, components._type for what matched, and a confidence of 1 to 10 from bounding-box size; countrycode and language parameters narrow and localise. source |
| Radar D Radar Labs, Inc. | /v1/geocode/forward returns structured address parts with countryCode and a confidence of exact, interpolated or fallback, and address-level coverage is published per country; partial inputs go to /search/autocomplete. source |
| Stadia Maps B Stadia Maps, Inc. | Search and structured search return match_type (exact, interpolated, fallback), where a missing house number falls back to the locality and says so, plus layers, confidence and country fields; autocomplete handles partial input. source |
| Woosmap C WOOSMAP SAS | /localities/geocode returns geometry.location_type (ROOFTOP, RANGE_INTERPOLATED, GEOMETRIC_CENTER, APPROXIMATE, POSTAL_CODE, DISTRICT), address components and scores_per_components, with language and autocomplete for partial input. source |
Does the job, with a limit 7
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.
| Listing | Why |
|---|---|
| Geoapify Location Platform + MCP C KEPTAGO LTD | Forward geocoding returns result_type, rank.confidence (with city, street and building levels) and rank.match_type, plus structured parameters. A first-hand report found search matched only whole, correctly accented words; autocomplete matched prefixes. source |
| Geocodio BB Dotsquare LLC | Each result carries accuracy, accuracy_type (rooftop, range_interpolation, street_center, place, county, state) and match_type, with no-result shown as nulls, but only for the US, Canada, Mexico, the UK, Australia and New Zealand. source |
| LocationIQ B Unwired Labs (India) Pvt Ltd | /search and /search/structured return coordinates, address parts and a matchquality object (matchcode, matchtype, matchlevel from venue and building down), but first-hand reports say quality breaks down at street-address level and small venues are missing. source |
| MapQuest F Mapquest Holdings LLC | /geocoding/v1/address returns latitude and longitude with status codes in info.statuscode (610 for ambiguous), but the reference page read shows no match-precision field to threshold on, and coverage outside the US is not stated. source |
| MapTiler Cloud B MapTiler AG | Forward geocoding returns GeoJSON features with place_type, relevance, country_code and context, with fuzzyMatch on by default and autocomplete, but relevance is a score, not a rooftop or interpolated level, and a first-hand report found name-plus-address venue queries returned nothing. source |
| Nominatim B Nominatim project (osm-search) | Search takes free text or structured fields with countrycodes and returns addresstype and place_rank to tell a house from a town, or an empty list. First-hand reports: no match after one or two typos, and no house number in OSM means a street or no answer. source |
| TomTom Maps APIs + MCP D TomTom International BV | A Geocoding API and fuzzy Search API exist with countrySet filters, but the geocode reference did not load (404 on the Markdown path), so the match type and confidence fields could not be confirmed. source |
What stops agents finishing
- address has no house number in the provider's data, so the answer is a street or town centroid
- one typo returns nothing
- postcode with a space or a new national format is not parsed
- MCP calls a legacy endpoint the key is not enabled for
Around it
Before: chat.user-gives-address, document-extraction.address-from-text, web-scrapers.page-to-markdown. After: maps.travel-time-route, maps.find-places-nearby, weather.forecast-for-place.
Where this comes from
Weight 24 of 100 in Maps, geocoding & places: 14 of 53 accounts (typos, postcodes, ranking, missing house numbers, venue names); the most described job, held at its share
The same as data: /api/v1/use-cases/maps.address-to-coordinates.json, or the MCP tool get_use_case with id maps.address-to-coordinates. Other jobs in this category: /api/v1/niches?category=maps.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.