# MapTiler Cloud vs Woosmap

> MapTiler Cloud scores 62.1 (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/maptiler-vs-woosmap
- Markdown: https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md (~4,450 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

MapTiler Cloud scores 62.1 (B) on agent readiness against Woosmap's 59.4 (C), and leads in 4 of 7 scored categories. Woosmap leads on reliability and agent ergonomics. Both do geocoding.

- MapTiler Cloud: grade B, 62.1/100, rank #574 of 1486. Markdown https://www.anchorterminal.com/tools/maptiler.md · JSON https://www.anchorterminal.com/api/v1/tools/maptiler.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

### MapTiler Cloud (B)

Good for: Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.

Ahead on:
- Security & auth, 64 against 43
- Payments & pricing, 40 against 30
- Maintenance & community, 70 against 26
- Transparency & trust, 80 against 54

Watch for: The API key is always sent as a query parameter

### 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 43
- Agent ergonomics, 76 against 70

Also in its favour:
- A hosted endpoint, with nothing to install

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


## Why the edge

### Maintenance & community: MapTiler Cloud +44

- MapTiler Cloud (70): @maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70.
- 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.

### Reliability: Woosmap +35

- MapTiler Cloud (43): Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43.
- 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.

### Transparency & trust: MapTiler Cloud +26

- MapTiler Cloud (80): Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64.
- 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.

### Security & auth: MapTiler Cloud +21

- MapTiler Cloud (64): Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64.
- Woosmap (43): Public keys are read-only and must carry a domain or IP restriction. Private keys are read-only or read and write (fixed at creation), restricted by IP, iOS or Android, and can go in an X-Api-Key header. Less 10 because `private_key` in the query string is a documented option and the default in the spec (17). Read-only keys and the read/write split give least privilege; no confirmation step on dataset deletes was found (16). find_nearby and get_place_details return public POI data, ratings and opening hours, with no prompt-injection guidance (7). Console usage per project wasn't checked (3). www.woosmap.com/.well-known/security.txt returns 404, and we found no disclosure policy, bug bounty or certification (0). 17+16+7+3+0 = 43.

### Payments & pricing: MapTiler Cloud +10

- MapTiler Cloud (40): No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-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.

### Agent ergonomics: Woosmap +6

- MapTiler Cloud (70): API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.
- Woosmap (76): API reading, with the hosted MCP server's nine tools as a second surface. Localities and Stores responses can be narrowed by type, components and fields, and the MCP set is small (20). Store search takes query filters, radius and paging, and the Distance Matrix has an async mode for large jobs (17). Documented error codes including 402 for billing and 429 with reset timing (17). Reads are safe to retry, but no idempotency key was found for the Datasets and Stores write endpoints, and the MCP docs don't mention tool annotations (10). Official JavaScript, iOS and Android SDKs and samples in Python and JavaScript, with few required parameters (12). 20+17+17+10+12 = 76.

## Score by category

| Category | Weight | MapTiler Cloud | Woosmap | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 43 | 78 | Woosmap +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 81 | Woosmap +2 |
| Agent ergonomics | 13% (16.2 this run) | 70 | 76 | Woosmap +6 |
| Security & auth | 14% (17.5 this run) | 64 | 43 | MapTiler Cloud +21 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | MapTiler Cloud +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 26 | MapTiler Cloud +44 |
| Transparency & trust | 7% (8.8 this run) | 80 | 54 | MapTiler Cloud +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.1 · B** | **59.4 · C** | |

## Facts side by side

| Fact | MapTiler Cloud | Woosmap |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | MapTiler AG | WOOSMAP SAS |
| Hosted endpoint | no (local only) | `https://api.woosmap.com/mcp` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 9 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-02 | none |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2024-07-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 | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 115k npm/wk | none |

## Verdicts

**MapTiler Cloud.** MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.

**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

### MapTiler Cloud

1. Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL
2. Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address
3. Use api.maptiler.eu when the user's requests must stay in the EU
4. Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt
5. Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution

### 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, MapTiler Cloud or Woosmap?

MapTiler Cloud scores 62.1 (B) on agent readiness against Woosmap's 59.4 (C), and leads in 4 of 7 scored categories. Woosmap leads on reliability and agent ergonomics.

### Do MapTiler Cloud and Woosmap need an API key?

Both need an API key.

### Can an agent call MapTiler Cloud and Woosmap without installing anything?

No hosted endpoint is listed for MapTiler Cloud. Woosmap has a hosted endpoint at https://api.woosmap.com/mcp.


## For agents

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

## Other comparisons with MapTiler Cloud or Woosmap

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