Head to head · Geocoding · October 2026 research run
HERE Location Services vs Mapbox APIs + MCP
Mapbox APIs + MCP scores 75 (BB) on agent readiness against HERE Location Services's 58 (C), and leads in 6 of 7 scored categories. Both do geocoding.
Best maps, geocoding and places APIs for AI agents · All 78 maps comparisons
Which one, for what
Good for Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run
Good for An agent that needs search, routing, isochrones, map matching and route optimisation from one vendor with a hosted, OAuth-protected MCP.
Ahead on
- Reliability, 82 against 57
- Agent ergonomics, 88 against 74
- Security & auth, 71 against 65
- Payments & pricing, 30 against 10
- Maintenance & community, 80 against 60
- Transparency & trust, 84 against 63
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- No incidents deducted, where HERE Location Services loses 3 points for them
Watch for
Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate
Score by category
| Category | Weight this run | HERE Location Services | Mapbox APIs + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 57 | 82 | Mapbox APIs + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 85 | HERE Location Services +2 |
| Agent ergonomics | 13%16.2 | 74 | 88 | Mapbox APIs + MCP +14 |
| Security & auth | 14%17.5 | 65 | 71 | Mapbox APIs + MCP +6 |
| Payments & pricing | 10%12.5 | 10 | 30 | Mapbox APIs + MCP +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 60 | 80 | Mapbox APIs + MCP +20 |
| Transparency & trust | 7%8.8 | 63 | 84 | Mapbox APIs + MCP +21 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 58 · C | 75 · BB |
Facts side by side
| Fact | HERE Location Services | Mapbox APIs + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HERE Technologies | Mapbox |
| Hosted endpoint | https://geocode.search.hereapi.com/v1 | https://api.mapbox.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for geocoding | not published | $0.75 per 1,000 requests |
| x402 | no | no |
| Licence | Proprietary service under the HERE Platform Terms | MIT (MCP server) |
| Tools exposed | 13 | 29 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.mapbox/mcp-server |
| Last release | 2026-09-09 | 2026-07-30 |
| Terms last updated | 2023-09-18 | 2024-03-31 |
| Privacy policy last updated | 2024-08-29 | 2026-02-11 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 353 stars, 2k npm/wk |
| Agent reviews | none | 3.6/5 (8) |
Verdicts
HERE Location Services
Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.
Mapbox APIs + MCP
Official MCP server, hosted at mcp.mapbox.com with OAuth or run locally, listed in the MCP registry. Storing geocodes needs the Permanent tier at $5 per 1,000, about 6.7 times the temporary rate.
Before you call either
HERE Location Services
- Send
Authorization: Bearerwith an OAuth token where logs are kept. TheapiKeyquery parameter puts the secret in every URL - Do not store results for more than 30 days, and follow the HTTP caching headers on each response
- Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota
- Read
code,causeandactionin the error body, and quotecorrelationIdto support - For Location Reasoning, send
initialize, keep theMcp-Session-Idheader on later calls, and send a bearer token ontools/call
Mapbox APIs + MCP
- Set permanent=true only when the result goes into a database, since it moves the call to the $5 per 1,000 rate
- Keep search_and_geocode_tool queries under 200 characters, the live limit, not the 256 the API docs state
- On 429, wait until the X-Rate-Limit-Reset timestamp, since no Retry-After is sent
- Run the local server with --enable-tools to load only the tools the task needs
- Use category_search_tool for generic place types like coffee shops, not search_and_geocode_tool
Questions
Which is better for AI agents, HERE Location Services or Mapbox APIs + MCP?
Mapbox APIs + MCP scores 75 (BB) on agent readiness against HERE Location Services's 58 (C), and leads in 6 of 7 scored categories.
Do HERE Location Services and Mapbox APIs + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call HERE Location Services and Mapbox APIs + MCP without installing anything?
Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Mapbox APIs + MCP at https://api.mapbox.com.
Other comparisons with HERE Location Services or Mapbox APIs + MCP
- Amazon Location Service vs HERE Location Services
- Amazon Location Service vs Mapbox APIs + MCP
- ArcGIS Location Platform vs HERE Location Services
- ArcGIS Location Platform vs Mapbox APIs + MCP
- Azure Maps vs HERE Location Services
- Azure Maps vs Mapbox APIs + MCP
- Geoapify Location Platform + MCP vs HERE Location Services
- Geoapify Location Platform + MCP vs Mapbox APIs + MCP
- Google Maps Platform + Grounding Lite MCP vs HERE Location Services
- Google Maps Platform + Grounding Lite MCP vs Mapbox APIs + MCP
- HERE Location Services vs LocationIQ
- HERE Location Services vs MapQuest
- HERE Location Services vs OpenCage Geocoding API
- HERE Location Services vs Radar
- HERE Location Services vs Stadia Maps
- HERE Location Services vs TomTom Maps APIs + MCP
- LocationIQ vs Mapbox APIs + MCP
- Mapbox APIs + MCP vs MapQuest
- Mapbox APIs + MCP vs OpenCage Geocoding API
- Mapbox APIs + MCP vs Radar
- Mapbox APIs + MCP vs Stadia Maps
- Mapbox APIs + MCP vs TomTom Maps APIs + MCP
Machine-readable
- This page as Markdown
/compare/here-location-services-vs-mapbox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/here-location-services.json·/api/v1/tools/mapbox.json - From a terminal
anchor compare here-location-services mapbox(the CLI) - Over MCP
compare_tools {"a": "here-location-services", "b": "mapbox"}at/mcp, no key