# Stadia Maps vs Woosmap

> Stadia Maps scores 65.2 (B) to Woosmap's 59.4 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap
- Markdown: https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md (~4,150 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Stadia Maps scores 65.2 (B) on agent readiness against Woosmap's 59.4 (C), and leads in 5 of 7 scored categories. Woosmap leads on reliability. Both do geocoding.

- Stadia Maps: grade B, 65.2/100, rank #431 of 1486. Markdown https://www.anchorterminal.com/tools/stadia-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/stadia-maps.json
- Woosmap: grade C, 59.4/100, rank #704 of 1486. Markdown https://www.anchorterminal.com/tools/woosmap.md · JSON https://www.anchorterminal.com/api/v1/tools/woosmap.json
- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md
- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md

## Which one, for what

### Stadia Maps (B)

Good for: Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.

Ahead on:
- Schema & documentation, 86 against 81
- Payments & pricing, 40 against 30
- Maintenance & community, 80 against 26
- Transparency & trust, 76 against 54

Also in its favour:
- Runs on your own machine

Watch for: Free plan is for development, testing and demos only

### Woosmap (C)

Good for: Store locators, address autocomplete and distance for retail and logistics teams that keep their own location data in the platform, with an MCP server for agents.

Ahead on:
- Reliability, 78 against 63

Watch for: No public changelog or release notes for the APIs


## Why the edge

### Maintenance & community: Stadia Maps +54

- 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.
- Woosmap (26): No dated API release, changelog or release note found. The newest dated activity we saw is the public woosmap-samples repository on 16 September 2026, which isn't an API release (10). No dated changes to count in the last 90 days (0). Support by email and a support centre, with no public changelog (5). Official JavaScript, iOS and Android SDKs exist, but we couldn't check their versions because the GitHub API was rate-limited and two SDK repository names didn't resolve; the MCP server isn't in the official MCP registry (8). The samples carry tests, per the rate-limits page (3). 10+0+5+8+3 = 26.

### Transparency & trust: Stadia Maps +22

- 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.
- Woosmap (54): Editorial half only. Closed service under online terms that name WOOSMAP SAS of Montpellier and the Commercial Court of Paris (15). The privacy policy covers website visitors only, and we found no statement on how long API request data is kept (5). The pricing page says the Address API is 'being deprecated for Pro Plan subscriptions', with no date (5). The legal notice says the site is hosted by Amazon Web Services; no sub-processor list or data location for the APIs was found (6). 15+5+5+6 = 31.

### Reliability: Woosmap +15

- 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.
- Woosmap (78): Hosted lines. Atlassian Statuspage at status.woosmap.com with seven components (Localities, Store Search, Geolocation, Distance, Address, Map and Indoor APIs) (20). The status home page lists no incidents from 23 October to 6 November 2026. The full history page loads by script and the site's robots.txt disallows /api/, so the rest of the 90 days wasn't read and the line is held between the unreadable and minor tiers (10). Each endpoint's reference states its own rate limit, such as 50 a second, shared by a project's keys (15). Every response carries RateLimit-Policy and RateLimit headers, and the rate-limits page says to wait `t` seconds after a 429, retry at most three times and back off 1, 2 and 4 seconds when the header is missing, with sample code (15). A 99.9% SLA on the Enterprise plan per the pricing page; we didn't read its terms (8). GA (10). 20+10+15+15+8+10 = 78.

### Payments & pricing: Stadia Maps +10

- Stadia Maps (40): 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.
- Woosmap (30): No x402, MPP or L402 (0). Plans and per-API tier breakpoints are public, but per-request prices sit in a script-driven calculator we couldn't read, so plan-only credit (10). Free plan up to 10,000 requests a month with 'No Credit Card Required' (20). A person signs up and creates a key in the console (0). 0+10+20+0 = 30.

### Schema & documentation: Stadia Maps +5

- 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.
- Woosmap (81): OpenAPI 3.1 spec, version 1.46.3, with 47 paths across Localities, Stores, Distance, Datasets, Indoor, Map and what3words endpoints (25). llms.txt as a routing index, llms-full.txt and a Markdown twin of every page (10). llms.txt says which pages are authoritative for parameters and which explain products, and endpoint pages describe purpose, with little on when not to call one (15). Typed parameters from the spec with enums and required fields (13). The spec documents 400, 401, 402, 403, 404, 409, 422 and 429 responses, and pages carry examples (13). The spec is versioned, but no public changelog or release notes were found (developers.woosmap.com/changelog/ and /release-notes/ return 404) (5). 25+10+15+13+13+5 = 81.

## Score by category

| Category | Weight | Stadia Maps | Woosmap | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 63 | 78 | Woosmap +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 81 | Stadia Maps +5 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 76 | Stadia Maps +4 |
| Security & auth | 14% (17.5 this run) | 40 | 43 | Woosmap +3 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Stadia Maps +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 26 | Stadia Maps +54 |
| Transparency & trust | 7% (8.8 this run) | 76 | 54 | Stadia Maps +22 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.2 · B** | **59.4 · C** | |

## Facts side by side

| Fact | Stadia Maps | Woosmap |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Stadia Maps | WOOSMAP SAS |
| Hosted endpoint | `https://api.stadiamaps.com` | `https://api.woosmap.com/mcp` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| Price for geocoding | $0.40 per 1,000 requests | not published |
| x402 | no | no |
| Licence | BSD-3-Clause (MCP server) | none |
| Tools exposed | 6 | 9 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-26 | none |
| Terms last updated | 2026-03-18 | no date given |
| Privacy policy last updated | 2026-10-01 | 2024-07-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 23 stars, 6.1k npm/wk, 192 PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

## How the scores have moved

### Stadia Maps

- -0.3 on 8 October 2026: checklist

### Woosmap

No score change since it was listed.

## Verdicts

**Stadia Maps.** Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.

**Woosmap.** Woosmap publishes an OpenAPI 3.1 spec, llms.txt with Markdown pages, per-endpoint rate limits and 429 retry rules, plus a hosted nine-tool MCP server. No changelog, security.txt, API data retention statement or readable per-request price was found, and private keys can travel in the query string.

## Before you call either

### Stadia Maps

1. Send the key as `Authorization: Stadia-Auth <key>` rather than in the URL
2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough
3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent
4. Don't write geocodes to a database on Free or Starter
5. Use bulk-geocode for addresses only, not POI names

### Woosmap

1. Send the private key in the X-Api-Key header, not the private_key query parameter
2. Use a read-only private key for the MCP server unless the task writes stores or datasets
3. On 429 wait the `t` seconds from the RateLimit header, retry at most three times, and pause batches when `r` reaches 0
4. Use find_stores_nearby for the customer's own locations and find_nearby for public POIs
5. Read endpoint parameters from the /api-reference/ Markdown pages, which llms.txt marks as authoritative

## Questions

### Which is better for AI agents, Stadia Maps or Woosmap?

Stadia Maps scores 65.2 (B) on agent readiness against Woosmap's 59.4 (C), and leads in 5 of 7 scored categories. Woosmap leads on reliability.

### Do Stadia Maps and Woosmap need an API key?

Both need an API key.

### Can an agent call Stadia Maps and Woosmap without installing anything?

Yes. Stadia Maps has a hosted endpoint at https://api.stadiamaps.com and Woosmap at https://api.woosmap.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "stadia-maps", "b": "woosmap"}`. From a terminal: `anchor compare stadia-maps woosmap`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/stadia-maps.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json

## Other comparisons with Stadia Maps or Woosmap

- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md)
- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)
- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)
- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)
- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)
- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)
- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)
- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)
- [Geocodio vs Stadia Maps](https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md)
- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)
- [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md)
- [Google Maps Platform + Grounding Lite MCP vs Woosmap](https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.md)
- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md)
- [HERE Location Services vs Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md)
- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)
- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md)
- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)
- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md)
- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)
- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md)
- [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md)
- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)
- [Nominatim vs Stadia Maps](https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.md)
- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)
- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)
- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-vs-woosmap.md)
- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)
- [Radar vs Woosmap](https://www.anchorterminal.com/compare/radar-vs-woosmap.md)
- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)
- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md)
- [NextBillion.ai vs Stadia Maps](https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.md)
- [NextBillion.ai vs Woosmap](https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp