Head to head · Geocoding · October 2026 research run
OpenCage Geocoding API vs Stadia Maps
OpenCage Geocoding API scores 69.8 (B) on agent readiness against Stadia Maps's 67.7 (B), and leads in 5 of 7 scored categories. Stadia Maps leads on schema & documentation and payments & pricing. Both do geocoding.
Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons
Which one, for what
Best for Bulk or repeated geocoding where results go into a database, and for EU data residency.
Ahead on
- Reliability, 85 against 63
- Agent ergonomics, 86 against 80
- Maintenance & community, 86 against 80
- Transparency & trust, 85 against 76
Watch for
Geocoding only, no place search or routing
Best for Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.
Ahead on
- Schema & documentation, 86 against 77
- Payments & pricing, 60 against 53
Also in its favour
- No incidents deducted, where OpenCage Geocoding API loses 3 points for them
Watch for
Free plan is for development, testing and demos only
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability OpenCage Geocoding API +22
OpenCage Geocoding API 85
Instatus page at status.opencagedata.com, measured by StatusCake, with forward geocoding, reverse geocoding, geosearch, the website and email sending as components (20). The incident history feed, read on 1 November 2026, lists nothing since the 26 June 2026 email outage, so the last 90 days are clean (30). Free trial limits of 2,500 a day and 1 a second, and per-second rates for each paid plan (15). 402 for a spent quota and 429 for going too fast are separate codes, and free and one-time plans get X-RateLimit-Limit, -Remaining and -Reset. There's no backoff guidance beyond '408 means try again' (10). No SLA found (0). GA (10).
Stadia Maps 63
Instatus page with 27 components across maps, routing, geocoding and data APIs, plus RSS and Atom history back to April 2025 (20). One incident in the 90 days to 2 November (history feed re-read on 2 November), on 25 September 2026, when a software update on edge nodes caused elevated request errors "in the initial deployment regions" across 24 listed components from 10:20 to 10:22 UTC before it was rolled back. Limited to some regions and two minutes, so minor (20). The FAQ says there's no fixed requests-a-second limit and the cap is the monthly credit pool, with credits per call published (12). A 429 is what you get when credits run out until the next cycle, with no Retry-After and no backoff guidance, so an agent can't tell a spent month from a burst (3). No SLA. The terms say the service is provided as is (0). The APIs are GA, but the MCP server has no release (8). 20+20+12+3+0+8 = 63.
Schema & documentation Stadia Maps +9
OpenCage Geocoding API 77
No OpenAPI. The MCP's three tools have JSON Schema inputs, and the REST API is one endpoint described parameter by parameter (15). llms.txt with 70 or more Markdown pages, including the API reference, pricing, terms and the MCP tutorial (10). The API reference explains each parameter and when to use it, but the MCP descriptions are one line each with no when-not-to-use (12). min and max on latitude, longitude and limit, but countrycode and bounds are free strings (10). A status code table and 23 tutorials across languages (15). v1 in the path and a dated API changelog in OpenCageData/opencagedata-misc-docs, newest entry 15 October 2026 (15).
Stadia Maps 86
Public OpenAPI 3.1.0 document at api.stadiamaps.com/openapi.yaml, version 11.1.0 (re-read on 2 November), from which the TypeScript and Python SDKs are generated (25). llms.txt at docs.stadiamaps.com, re-read on 2 November (10). The MCP's six tool descriptions say when not to use a tool, for example bulk-geocode warns against POI names (14). Zod inputs with minimums such as at least two route locations, but some fields are loose strings (12). Docs examples per endpoint. We didn't read an error reference (10). A dated public changelog with 14 entries between 12 August and 26 October 2026 and a Keep a Changelog file in each SDK (15). 25+10+14+12+10+15 = 86.
Transparency & trust OpenCage Geocoding API +9
OpenCage Geocoding API 85
Closed service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20).
Stadia Maps 76
Closed service with clear terms, last updated 18 March 2026, a BSD-3-Clause MCP server and open-source SDKs (20). Server logs kept about 7 to 14 days, account data deleted within 30 days of closure, a DPA, and per-plan storage rules spelt out. The privacy policy was updated 1 October 2026 (28). No deprecation policy. The terms promise 30 days' notice for fee increases and reasonable efforts for other material changes (6). Third-party processors listed with locations in the privacy policy, and hosting described as primarily US (18). 20+28+6+18 = 72.
Payments & pricing Stadia Maps +7
OpenCage Geocoding API 53
No x402, MPP or L402 (0). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Stadia Maps 60
No x402, MPP or L402 (0). Credit costs per call and per-1,000-credit overage ($0.03, $0.02 and $0.015) published without login, re-read on 2 November (20). Free tier of 200,000 credits a month and a 14-day Professional trial without a credit card, though the free tier doesn't allow commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics OpenCage Geocoding API +6
OpenCage Geocoding API 86
Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15).
Stadia Maps 80
Six MCP tools, pared down on 20 June 2025 'to save on context tokens' (25). size, layers, boundary filters and focus points on geocoding, and a bulk geocoding endpoint (18). The same 429 means a burst or a spent month, which costs a turn to work out (12). Every call reads, but the MCP tools carry no readOnlyHint or other annotations (10). Official generated SDKs in TypeScript and Python, with sensible defaults (15). 25+18+12+10+15 = 80.
Maintenance & community OpenCage Geocoding API +6
OpenCage Geocoding API 86
The newest API changelog entry is 15 October 2026 (SMDG port terminal codes), and the Python SDK released 3.5.0 on 28 October 2026, both within 30 days (30). Dated changes in the last 90 days include improved IATA airport code geocoding (blog, 7 October), the 15 October changelog entry and Python SDK 3.5.0, with spreadsheet upload improvements on 14 August (20). Dependabot pull requests on the MCP repo are merged within days, the latest on 1 November. We couldn't see issue reply times from git (15). In the official MCP registry as io.github.OpenCageData/opencage-geocoding-mcp, and the Python SDK is current at 3.5.0 (15). The MCP's CI lints, type-checks and builds on Node 20, 22 and 24 but runs no tests, and npm still serves 1.0.3 from 11 September 2025 while the repo is at 1.0.5 (6).
Stadia Maps 80
Changelog entry on 26 October 2026, a forward geocoding fix for Unicode edge cases (30). 14 dated changelog entries between 12 August and 26 October 2026, among them the 20 October Static Maps rebuild and the 17 October geocoding data release (20). A public changelog and support desk, but the MCP repo's last commit is still 29 July 2025 on 2 November (10). Official TypeScript SDK v9.1.0 and Python SDK v8.1.0, both tagged 27 April 2026 and still the newest tags (15). SDK CI runs integration tests against the live API, but the MCP server has no CI, no tagged release, no npm package and no registry entry (5). 30+20+10+15+5 = 80.
Score by category
| Category | Weight | OpenCage Geocoding API | Stadia Maps | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 63 | OpenCage Geocoding API +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 86 | Stadia Maps +9 |
| Agent ergonomics | 13% | 86 | 80 | OpenCage Geocoding API +6 |
| Security & auth | 14% | 44 | 40 | OpenCage Geocoding API +4 |
| Payments & pricing | 10% | 53 | 60 | Stadia Maps +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 86 | 80 | OpenCage Geocoding API +6 |
| Transparency & trust | 7% | 85 | 76 | OpenCage Geocoding API +9 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 69.8/100 | B 67.7/100 |
Facts side by side
| Fact | OpenCage Geocoding API | Stadia Maps |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | OpenCage | Stadia Maps |
| Hosted endpoint | https://api.opencagedata.com/geocode/v1/json | https://api.stadiamaps.com |
| Transports | HTTP, stdio | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Paid | Freemium |
| Price for geocoding | not published | $0.40 per 1,000 requests |
| x402 | no | no |
| Licence | MIT (MCP server) | BSD-3-Clause (MCP server) |
| Tools exposed | 3 | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.OpenCageData/opencage-geocoding-mcp | not listed |
| Last release | 2026-10-28 | 2026-10-26 |
| Terms last updated | no date given | 2026-03-18 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| 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 | 19 stars, 5.5k npm/wk, 138k PyPI/wk | 23 stars, 6.1k npm/wk, 192 PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | OpenCage Geocoding API | Stadia Maps |
|---|---|---|
| BuoyAutonomous onboarding tester | 3/5 A two-step trial that is for testing only | 3/5 Two steps and a 14-day Professional trial |
| LedgerCost analyst | 4/5 One-time packs from $1.75 per 1,000, and storage is free | 4/5 $0.40 per 1,000 geocodes on Starter, at 20 credits each |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
OpenCage Geocoding API
OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.
Stadia Maps
Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.
Before you call either
OpenCage Geocoding API
- Add no_annotations=1 and limit=1 when you only need coordinates
- Stop on 402, which means the day's quota is gone, and back off on 429
- Add no_record=1 when the query holds personal data, and redact the key parameter before logging request URLs
- On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions
- Credit OpenStreetMap wherever you show results
Stadia Maps
- Send the key as
Authorization: Stadia-Auth <key>rather than in the URL - Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough
- Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent
- Don't write geocodes to a database on Free or Starter
- Use bulk-geocode for addresses only, not POI names
Questions
Which is better for AI agents, OpenCage Geocoding API or Stadia Maps?
OpenCage Geocoding API scores 69.8 (B) on agent readiness against Stadia Maps's 67.7 (B), and leads in 5 of 7 scored categories. Stadia Maps leads on schema & documentation and payments & pricing.
Do OpenCage Geocoding API and Stadia Maps need an API key?
Both need an API key.
Can an agent call OpenCage Geocoding API and Stadia Maps without installing anything?
Yes. OpenCage Geocoding API has a hosted endpoint at https://api.opencagedata.com/geocode/v1/json and Stadia Maps at https://api.stadiamaps.com.
Other comparisons with OpenCage Geocoding API or Stadia Maps
- Amazon Location Service vs OpenCage Geocoding API
- Amazon Location Service vs Stadia Maps
- ArcGIS Location Platform vs OpenCage Geocoding API
- ArcGIS Location Platform vs Stadia Maps
- Azure Maps vs OpenCage Geocoding API
- Azure Maps vs Stadia Maps
- Geoapify Location Platform + MCP vs OpenCage Geocoding API
- Geoapify Location Platform + MCP vs Stadia Maps
- Geocodio vs OpenCage Geocoding API
- Geocodio vs Stadia Maps
- Google Maps Platform + Grounding Lite MCP vs OpenCage Geocoding API
- Google Maps Platform + Grounding Lite MCP vs Stadia Maps
- HERE Location Services vs OpenCage Geocoding API
- HERE Location Services vs Stadia Maps
- LocationIQ vs OpenCage Geocoding API
- LocationIQ vs Stadia Maps
- Mapbox APIs + MCP vs OpenCage Geocoding API
- Mapbox APIs + MCP vs Stadia Maps
- MapQuest vs OpenCage Geocoding API
- MapQuest vs Stadia Maps
- MapTiler Cloud vs OpenCage Geocoding API
- MapTiler Cloud vs Stadia Maps
- NextBillion.ai vs OpenCage Geocoding API
- Nominatim vs OpenCage Geocoding API
- Nominatim vs Stadia Maps
- OpenCage Geocoding API vs Radar
- OpenCage Geocoding API vs TomTom Maps APIs + MCP
- OpenCage Geocoding API vs Woosmap
- Radar vs Stadia Maps
- Stadia Maps vs TomTom Maps APIs + MCP
- Stadia Maps vs Woosmap
- NextBillion.ai vs Stadia Maps
Machine-readable
- This page as Markdown
/compare/opencage-vs-stadia-maps.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/opencage.json·/api/v1/tools/stadia-maps.json - From a terminal
anchor compare opencage stadia-maps(the CLI) - Over MCP
compare_tools {"a": "opencage", "b": "stadia-maps"}at/mcp, no key