# MapQuest vs OpenCage Geocoding API (slim)

> OpenCage Geocoding API scores 69.2 (B) on agent readiness against MapQuest's 35.1 (F), and leads in every scored category. Both do geo geocode. Category scores, facts, verdicts and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mapquest-vs-opencage.md (~2,200 tokens) · this version ~730 tokens · JSON https://www.anchorterminal.com/compare/mapquest-vs-opencage.json · canonical https://www.anchorterminal.com/compare/mapquest-vs-opencage
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08

OpenCage Geocoding API scores 69.2 (B) on agent readiness against MapQuest's 35.1 (F), and leads in every scored category. Both do geo geocode.

- MapQuest: F 35.1, rank #710 of 722 · https://www.anchorterminal.com/tools/mapquest.min.md
- OpenCage Geocoding API: B 69.2, rank #164 of 722 · https://www.anchorterminal.com/tools/opencage.min.md
- MapQuest, good for An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.
- OpenCage Geocoding API, good for Bulk or repeated geocoding where results go into a database, and for EU data residency. Ahead on Reliability, 85 against 23; Schema & documentation, 77 against 47; Agent ergonomics, 86 against 60; Security & auth, 47 against 28; Payments & pricing, 35 against 30; Maintenance & community, 66 against 23; Transparency & trust, 84 against 28. Also Runs on your own machine; Free to start without a card.

| Category | MapQuest | OpenCage Geocoding API |
| --- | --- | --- |
| Reliability (16%) | 23 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 47 | 77 |
| Agent ergonomics (13%) | 60 | 86 |
| Security & auth (14%) | 28 | 47 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 23 | 66 |
| Transparency & trust (7%) | 28 | 84 |

| Fact (where they differ) | MapQuest | OpenCage Geocoding API |
| --- | --- | --- |
| Vendor | MapQuest (System1) | OpenCage |
| Hosted endpoint | `https://www.mapquestapi.com` | `https://api.opencagedata.com/geocode/v1/json` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Paid |
| Licence | Proprietary service. No API terms were found published without a login | MIT (MCP server) |
| Tools exposed | none | 3 |
| MCP registry | not listed | `io.github.OpenCageData/opencage-geocoding-mcp` |
| Last release | 2026-07-16 | 2026-06-25 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models |  | not found in the text |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | not found in the text |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |
| Popularity | none | 19 stars, 5.5k npm/wk, 138k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |