Niches · Maps, geocoding & places
Geocode a list of addresses and keep the results
Two or three companies' docs show a full fit.
What counts as done
Every row comes back with coordinates and a precision level, in input order, through a batch endpoint or async job rather than one call per row; the terms on the plan used allow the results to be stored permanently and shown on a non-vendor map; repeat runs give the same answer for the same input.
Measured, for our own tests: 10,000 addresses finish within one hour at the published price. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: geocode the addresses in this spreadsheet
, add lat and long columns to my customer list
, clean and geocode these 20,000 addresses
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Geocodio BB Dotsquare LLC | Batch geocoding takes up to 10,000 addresses per call with results guaranteed in input order, and the Lists API runs async jobs. Terms section 8.4 lets results be stored and used beyond the term, with country-specific exceptions. source |
| Stadia Maps B Stadia Maps, Inc. | Bulk geocoding takes up to 5,000 queries a request and returns results in request order with a status per item; results may be stored permanently on Standard, Professional or Enterprise with no surcharge. source |
Does the job, with a limit 10
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 |
|---|---|
| Amazon Location Service A Amazon Web Services, Inc. | No batch geocode. The Jobs API runs only ValidateAddress, with Parquet in S3 and an IAM role a person sets up, returning Position as an option. Storing needs IntendedUse=Storage at $4.00 against $0.50 per 1,000. source |
| ArcGIS Location Platform B Environmental Systems Research Institute, Inc. | geocodeAddresses takes record sets up to the service's MaxBatchSize and returns ResultID to map rows back. Storing needs forStorage=true on pay-as-you-go at eight times the unstored rate, and display on a non-Esri map was not confirmed. source |
| Azure Maps B Microsoft Corporation | The batch endpoint takes 100 queries a call and returns batchItems in input order, so 10,000 rows means 100 calls. A first-hand report found the same address geocoded differently across identical parallel batch runs. source |
| Geoapify Location Platform + MCP C KEPTAGO LTD | Batch Geocoding is an async job of up to 1,000 addresses with a results URL, and the docs say results may be cached or stored with no limits, but that right is not in the terms and OSM attribution applies. source |
| Mapbox APIs + MCP A Mapbox, Inc. | The v6 batch endpoint takes up to 1,000 forward or reverse queries a request, and permanent=true allows storing indefinitely, but only with a card on file at $5 per 1,000, about 6.7 times the temporary rate. source |
| MapQuest F Mapquest Holdings LLC | Batch takes 100 addresses a call and the async batch job takes up to 1 million rows with status, results and errors endpoints, but storing geocodes was reported as barred outside Enterprise, and the plans page no longer renders for our reader. source |
| MapTiler Cloud B MapTiler AG | Batch geocoding packs semicolon-separated queries into one GET (up to 50), and the Cloud terms allow search results to be used outside the service and bulk geocoding with attribution, but 10,000 rows means 200 synchronous calls and no async job. source |
| NextBillion.ai C NextBillion.ai Pte. Ltd. | The batch geocode endpoint takes up to 100 queries a request, so 10,000 rows is 100 calls with no async job, and storage rights for results were not found in the docs read. source |
| OpenCage Geocoding API B OpenCage GmbH | The terms let results be cached or stored as long as you like on any plan, which first-hand accounts give as the reason to choose it, but there is no batch endpoint, so a list is one call per row at 15 a second on the smallest plan. source |
| TomTom Maps APIs + MCP D TomTom International BV | Batch Search runs synchronously for up to 100 items or asynchronously for up to 10,000 with submit and download steps, but the developer terms that set storage rights could not be read. source |
Doesn't do this job 6
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Google Maps Platform + Grounding Lite MCP BB Google LLC or a regional Google entity, by billing country | No batch geocoding endpoint, so a list is one call per row, and the terms allow caching coordinates for 30 days at most and only for display on a Google map. A first-hand report says the small print bars storing points. source |
| HERE Location Services C HERE Europe B.V. | Batch API v7 runs async jobs of up to 1 million records with recId mapping, but results may be kept for 30 days at most, and the Platform Terms bar use with an AI system. source |
| LocationIQ B Unwired Labs (India) Pvt Ltd | No batch or async geocoding endpoint in the API spec, so a list is one call per row within a daily quota; paid customers may store response data forever. source |
| Nominatim B Nominatim project (osm-search) | No batch endpoint, and the public instance allows 1 request a second with bulk geocoding discouraged; a self-hosted install has no limit but still means one call per row. Results may be kept under ODbL. source |
| Radar D Radar Labs, Inc. | No batch geocoding endpoint in the API reference, and responses may be cached for 30 days at most. source |
| Woosmap C WOOSMAP SAS | No batch or async geocoding endpoint is listed in the API index; geocode is one address per call at 50 a second, and data caching is an Enterprise option. source |
What stops agents finishing
- terms bar permanent storage, or charge several times the single-use rate for it
- public or free tier capped near 1 request a second or for development only
- no batch endpoint, so a large list becomes thousands of calls
- leaked or unscoped key runs up a bill with no spend cap
Around it
Before: spreadsheets.read-sheet, data.query-table, crm.export-contacts. After: spreadsheets.write-columns, data.write-rows, maps.travel-time-matrix.
Where this comes from
Weight 17 of 100 in Maps, geocoding & places: 10 of 53 accounts; storage terms are the most argued point in the April 2025 Hacker News geocoder thread (acc-01 to acc-05)
The same as data: /api/v1/use-cases/maps.batch-geocode-and-store.json, or the MCP tool get_use_case with id maps.batch-geocode-and-store. 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.