{ "data": { "a": { "slug": "stadia-maps", "name": "Stadia Maps", "vendor": "Stadia Maps", "vendorUrl": "https://stadiamaps.com", "kind": "http-api", "category": "maps", "summary": "Geocoding, reverse geocoding, autocomplete and place details, routing, matrix, isochrones, static maps and hosted vector, raster and satellite tiles, sold in credits on plans from $20 a month.", "url": "https://www.anchorterminal.com/tools/stadia-maps", "markdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stadia-maps.json", "dns": "stadia-maps.grade.anchorterminal.com", "repo": "https://github.com/stadiamaps/stadiamaps-mcp-server-ts", "license": "BSD-3-Clause (MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.stadiamaps.com", "packages": [ { "registry": "npm", "name": "@stadiamaps/api" }, { "registry": "pypi", "name": "stadiamaps" } ], "auth": "api-key", "authNotes": "API key as the api_key query parameter or in an `Authorization: Stadia-Auth \u003ckey\u003e` header. Browser apps can use domain-based auth with no key, checked against the Origin and Referer headers. The MCP server reads API_KEY.", "pricing": "freemium", "pricingNotes": "Free 200,000 credits a month for development, testing and demos only, no commercial use. Starter $20 a month (1 million credits), Standard $80 (7.5 million), Professional $250 (25 million), with overage at $0.03, $0.02 and $0.015 per 1,000 credits. A forward, reverse or structured geocode, a place lookup, an Autocomplete v1 search or a route is 20 credits, Autocomplete v2 is 1, a matrix element 10, a map tile 1 and a satellite tile 4, so Starter covers 50,000 geocodes. New accounts get a 14-day Professional trial with no card (https://stadiamaps.com/pricing/). When credits run out you get 429 until the next cycle unless pay-as-you-go is on (https://stadiamaps.com/faqs/).", "priceSummary": "$20 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": 23, "npmWeekly": 6058, "pypiWeekly": 192, "asOf": "2026-09-30" }, "docsUrl": "https://docs.stadiamaps.com", "llmsTxt": "https://docs.stadiamaps.com/llms.txt", "openapi": "https://api.stadiamaps.com/openapi.yaml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "llms-txt", "official", "typescript", "python", "free-tier", "no-card", "open-data" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 431, "ranked": true, "rankOf": 1486, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 80, "payments": 40, "reliability": 63, "schema": 86, "security": 40, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.", "bestFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.", "strengths": [ "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs", "Published credit costs, with 50,000 geocodes for $20 a month on Starter", "Header auth keeps the key out of URLs, and keys rotate through an API", "Server logs kept about 7 to 14 days, and a DPA", "14 dated changelog entries between June and September 2026" ], "weaknesses": [ "Free plan is for development, testing and demos only", "The same 429 signals a burst or a spent month of credits, with no Retry-After", "No SLA, no security.txt and no disclosure policy found", "MCP server has no release, no CI and no commits since 29 July 2025", "The terms forbid benchmarking against competitors without written permission" ], "agentNotes": [ "Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 80, "maintenance": 80, "payments": 40, "reliability": 63, "schema": 86, "security": 40, "transparency": 72 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-10-08", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"Authorization: Stadia-Auth $STADIA_API_KEY\" \"https://api.stadiamaps.com/geocoding/v1/search?text=10%20Downing%20Street%2C%20London\u0026size=1\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/stadia-maps" }, "area": "everyday", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 20, "note": "1 million credits, about 50,000 geocodes" }, { "item": "Standard plan", "unit": "month", "usd": 80, "note": "7.5 million credits, permanent geocode storage" }, { "item": "Professional plan", "unit": "month", "usd": 250, "note": "25 million credits" }, { "item": "Geocoding within Starter", "unit": "1k-requests", "usd": 0.4, "note": "20 credits each, $20 for 1 million credits" }, { "item": "Geocoding overage on Starter", "unit": "1k-requests", "usd": 0.6, "note": "20 credits each at $0.03 per 1,000 credits" } ], "provenance": { "legalEntity": "Stadia Maps, Inc.", "domain": "stadiamaps.com", "domainRegistered": "2016-11-30", "endpointOnVendorDomain": true, "terms": "https://stadiamaps.com/terms-of-service/", "privacy": "https://stadiamaps.com/privacy/privacy-policy/", "statusPage": "https://status.stadiamaps.com", "changelog": "https://stadiamaps.com/changelog/", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "The terms name Stadia Maps, Inc., a Delaware corporation with an address in East Lansing, Michigan, under Delaware law. Last updated 18 March 2026.", "Pages showing Traffic Products must carry \"© Stadia Maps © TomTom\".", "stadiamaps.com/.well-known/security.txt returned 404 on 2026-09-30 and again on 2026-11-02." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/stadia-maps.json", "live": { "slug": "stadia-maps", "probe": { "target": "https://api.stadiamaps.com", "method": "get", "lastAt": "2026-11-07T18:20:57.101069815Z", "lastOk": true, "lastStatus": 404, "lastMs": 98, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 38, "p95ms24h": 120, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.stadiamaps.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:48.860153105Z" }, "versions": [ { "registry": "npm", "name": "@stadiamaps/api", "version": "9.1.0", "seenAt": "2026-11-07T00:08:18.390771756Z" }, { "registry": "pypi", "name": "stadiamaps", "version": "8.1.0", "released": "2026-04-27", "seenAt": "2026-11-07T00:08:19.436197982Z" } ], "githubStars": 25, "npmWeekly": 5629, "pypiWeekly": 257, "securityTxt": { "url": "https://stadiamaps.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:53.421563591Z" }, "llmsTxt": { "url": "https://docs.stadiamaps.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:02.632314399Z" }, "domain": { "domain": "stadiamaps.com", "registered": "2016-11-30", "source": "https://rdap.verisign.com/com/v1/domain/stadiamaps.com", "checkedAt": "2026-11-01T14:16:14.439995302Z" }, "pages": [ { "url": "https://stadiamaps.com/changelog/", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:20:47.194860696Z", "changedAt": "2026-11-03T07:59:24.869309921Z", "fingerprint": "84f157f93d47" }, { "url": "https://stadiamaps.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:20:49.286778217Z", "changedAt": "2026-10-30T05:49:14.583115496Z", "fingerprint": "1129178e256e" }, { "url": "https://stadiamaps.com/privacy/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:20:51.230633816Z", "changedAt": "2026-10-30T05:49:16.651265989Z", "fingerprint": "dea22601908a" }, { "url": "https://stadiamaps.com/terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:20:53.28669173Z", "changedAt": "2026-10-30T05:49:18.614187045Z", "fingerprint": "f6e28a9f6a07" } ], "github": { "repo": "stadiamaps/stadiamaps-mcp-server-ts", "checkedAt": "2026-11-02T09:27:58.17869331Z", "stars": 25, "archived": false, "issuesEnabled": true, "pushedAt": "2025-07-29T09:13:45Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-07T18:20:57.101069815Z" } }, "answer": "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.", "b": { "slug": "woosmap", "name": "Woosmap", "vendor": "WOOSMAP SAS", "vendorUrl": "https://www.woosmap.com", "kind": "http-api", "category": "maps", "summary": "Woosmap is a French location platform with REST APIs for address autocomplete and geocoding (Localities), store search, distance and routing, geolocation, indoor maps and map display, plus a hosted MCP server for AI assistants.", "url": "https://www.anchorterminal.com/tools/woosmap", "markdownUrl": "https://www.anchorterminal.com/tools/woosmap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/woosmap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/woosmap.json", "dns": "woosmap.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.woosmap.com/mcp", "packages": [], "auth": "api-key", "authNotes": "Keys from the Woosmap Console after a browser signup. Public keys (woos-...) are read-only and must be restricted to domains or IPs. Private keys are read-only or read and write, fixed at creation, restricted by IP, iOS or Android, and sent as the X-Api-Key header or the private_key query parameter. The MCP server takes a private key in the X-Api-Key header.", "pricing": "freemium", "pricingNotes": "Free plan up to 10,000 API requests a month with no credit card. Pro uses public volume tiers per API, shown in a calculator, and can be bought through AWS Marketplace. Enterprise is by quote with volume discounts, data caching options and a 99.9% SLA.", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, llms.txt or pricing page (checked 2026-11-06). The spec documents a 402 response for billing, not a payment protocol.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developers.woosmap.com/", "llmsTxt": "https://developers.woosmap.com/llms.txt", "openapi": "https://developers.woosmap.com/assets/woosmap-openapi3.json", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "status-page", "enterprise", "sla", "eu", "android", "ios", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 59.4, "grade": "C", "agentReady": false, "rank": 704, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 26, "payments": 30, "reliability": 78, "schema": 81, "security": 43, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.1 spec with 47 paths, llms.txt routing index and Markdown twins of every page", "Per-endpoint rate limits with RateLimit headers and explicit 429 retry rules and sample code", "Hosted MCP server at api.woosmap.com/mcp with nine tools, including search over the customer's own store data", "Read-only and read/write private keys with IP, iOS or Android restrictions and an X-Api-Key header", "Free plan of 10,000 requests a month with no card" ], "weaknesses": [ "No public changelog or release notes for the APIs", "No security.txt, disclosure policy or certification found", "The privacy policy covers the website only, with nothing on API data retention", "Per-request prices aren't readable without the script-driven calculator", "`private_key` in the query string is documented and is the spec's default scheme" ], "agentNotes": [ "Send the private key in the X-Api-Key header, not the private_key query parameter", "Use a read-only private key for the MCP server unless the task writes stores or datasets", "On 429 wait the `t` seconds from the RateLimit header, retry at most three times, and pause batches when `r` reaches 0", "Use find_stores_nearby for the customer's own locations and find_nearby for public POIs", "Read endpoint parameters from the /api-reference/ Markdown pages, which llms.txt marks as authoritative" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.4 } ], "editorialScores": { "ergonomics": 76, "maintenance": 26, "payments": 30, "reliability": 78, "schema": 81, "security": 43, "transparency": 31 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"X-Api-Key: $WOOSMAP_PRIVATE_KEY\" \"https://api.woosmap.com/localities/geocode?address=Place+de+la+Comedie+Montpellier\"", "config": { "mcpServers": { "woosmap": { "args": [ "mcp-remote", "https://api.woosmap.com/mcp", "--header", "X-Api-Key: PRIVATE_KEY" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/woosmap" }, "area": "everyday", "provenance": { "legalEntity": "WOOSMAP SAS", "domain": "woosmap.com", "domainRegistered": "2010-06-04", "endpointOnVendorDomain": true, "terms": "https://www.woosmap.com/policies/terms-online", "privacy": "https://www.woosmap.com/policies/privacy", "statusPage": "https://status.woosmap.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The online terms name WOOSMAP, a French SAS at 5 rue du Plan du Palais, 34000 Montpellier, RCS Montpellier 983 770 405, represented by its CEO Jean-Thomas Rouzin. The legal notice (effective 1 July 2024) gives SAS capital of €10,821,200 and AWS as the site host.", "status.woosmap.com's robots.txt disallows /api/ and /embed/. A request to /api/v2/incidents.json was sent by mistake on 6 November 2026 before robots.txt was read; its contents are not used anywhere in this listing.", "www.woosmap.com/.well-known/security.txt returns 404.", "No public API changelog was found. developers.woosmap.com/changelog/ and /release-notes/ return 404.", "RDAP gives woosmap.com a registration date of 4 June 2010. robots.txt on www.woosmap.com and developers.woosmap.com allows these pages, and the developer site's robots.txt allows llms.txt by name." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/woosmap.json", "live": { "slug": "woosmap", "probe": { "target": "https://api.woosmap.com/mcp", "method": "get", "lastAt": "2026-11-07T18:21:05.894098339Z", "lastOk": true, "lastStatus": 401, "lastMs": 219, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 48, "p95ms24h": 118, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.woosmap.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:22:11.709282208Z" }, "securityTxt": { "url": "https://woosmap.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:21.81706489Z" }, "llmsTxt": { "url": "https://developers.woosmap.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:23.501072242Z" }, "pages": [ { "url": "https://www.woosmap.com/policies/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:37:14.116262014Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99523833ae5e" }, { "url": "https://www.woosmap.com/policies/terms-online", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:19.402817389Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6252e1bc3d91" } ], "updatedAt": "2026-11-07T18:22:11.709282208Z" } }, "edges": [ { "by": 54, "category": "maintenance", "leads": "stadia-maps", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 80, "b": 26 } }, { "by": 22, "category": "transparency", "leads": "stadia-maps", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 76, "b": 54 } }, { "by": 15, "category": "reliability", "leads": "woosmap", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 63, "b": 78 } }, { "by": 10, "category": "payments", "leads": "stadia-maps", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 40, "b": 30 } }, { "by": 5, "category": "schema", "leads": "stadia-maps", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 86, "b": 81 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Stadia Maps", "b": "WOOSMAP SAS", "name": "Vendor" }, { "a": "https://api.stadiamaps.com", "b": "https://api.woosmap.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$0.40 per 1,000 requests", "b": "not published", "name": "Price for geocoding" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "BSD-3-Clause (MCP server)", "b": "none", "name": "Licence" }, { "a": "6", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-26", "b": "none", "name": "Last release" }, { "a": "2026-03-18", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "2024-07-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "23 stars, 6.1k npm/wk, 192 PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, Stadia Maps or Woosmap?" }, { "answer": "Both need an API key.", "question": "Do Stadia Maps and Woosmap need an API key?" }, { "answer": "Yes. Stadia Maps has a hosted endpoint at https://api.stadiamaps.com and Woosmap at https://api.woosmap.com/mcp.", "question": "Can an agent call Stadia Maps and Woosmap without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 81", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 80 against 26", "Transparency \u0026 trust, 76 against 54" ], "also": [ "Runs on your own machine" ], "goodFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.", "slug": "stadia-maps", "watchFor": "Free plan is for development, testing and demos only" }, { "aheadOn": [ "Reliability, 78 against 63" ], "also": null, "goodFor": "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.", "slug": "woosmap", "watchFor": "No public changelog or release notes for the APIs" } ], "history": { "stadia-maps": [ { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 65.5, "fromGrade": "B", "to": 65.2, "toGrade": "B" } ], "woosmap": null }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json", "title": "Amazon Location Service vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.json", "title": "Amazon Location Service vs Woosmap", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.json", "title": "ArcGIS Location Platform vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-woosmap.json", "title": "ArcGIS Location Platform vs Woosmap", "url": "https://www.anchorterminal.com/compare/arcgis-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.json", "title": "Azure Maps vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.json", "title": "Azure Maps vs Woosmap", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.json", "title": "Geoapify Location Platform + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-woosmap.json", "title": "Geoapify Location Platform + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/geoapify-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.json", "title": "Geocodio vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap.json", "title": "Geocodio vs Woosmap", "url": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.json", "title": "Google Maps Platform + Grounding Lite MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.json", "title": "Google Maps Platform + Grounding Lite MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json", "title": "HERE Location Services vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.json", "title": "HERE Location Services vs Woosmap", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.json", "title": "LocationIQ vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap.json", "title": "LocationIQ vs Woosmap", "url": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.json", "title": "Mapbox APIs + MCP vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-woosmap.json", "title": "Mapbox APIs + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/mapbox-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json", "title": "MapQuest vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap.json", "title": "MapQuest vs Woosmap", "url": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.json", "title": "MapTiler Cloud vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap.json", "title": "MapTiler Cloud vs Woosmap", "url": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.json", "title": "Nominatim vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap.json", "title": "Nominatim vs Woosmap", "url": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.json", "title": "OpenCage Geocoding API vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-woosmap.json", "title": "OpenCage Geocoding API vs Woosmap", "url": "https://www.anchorterminal.com/compare/opencage-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps.json", "title": "Radar vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-woosmap.json", "title": "Radar vs Woosmap", "url": "https://www.anchorterminal.com/compare/radar-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap.json", "title": "TomTom Maps APIs + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.json", "title": "NextBillion.ai vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.json", "title": "NextBillion.ai vs Woosmap", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-woosmap" } ], "panel": null, "scores": [ { "by": 15, "edge": "woosmap", "key": "reliability", "name": "Reliability", "stadia-maps": 63, "weight": 16, "woosmap": 78 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "stadia-maps", "key": "schema", "name": "Schema \u0026 documentation", "stadia-maps": 86, "weight": 13, "woosmap": 81 }, { "by": 4, "edge": "stadia-maps", "key": "ergonomics", "name": "Agent ergonomics", "stadia-maps": 80, "weight": 13, "woosmap": 76 }, { "by": 3, "edge": "woosmap", "key": "security", "name": "Security \u0026 auth", "stadia-maps": 40, "weight": 14, "woosmap": 43 }, { "by": 10, "edge": "stadia-maps", "key": "payments", "name": "Payments \u0026 pricing", "stadia-maps": 40, "weight": 10, "woosmap": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 54, "edge": "stadia-maps", "key": "maintenance", "name": "Maintenance \u0026 community", "stadia-maps": 80, "weight": 7, "woosmap": 26 }, { "by": 22, "edge": "stadia-maps", "key": "transparency", "name": "Transparency \u0026 trust", "stadia-maps": 76, "weight": 7, "woosmap": 54 } ], "summary": "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.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap", "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.min.md" }, "markdown": "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.\n\n- 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\n- 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\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### Stadia Maps (B)\n\nGood for: Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 81\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 80 against 26\n- Transparency \u0026 trust, 76 against 54\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Free plan is for development, testing and demos only\n\n### Woosmap (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 78 against 63\n\nWatch for: No public changelog or release notes for the APIs\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Stadia Maps +54\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: Stadia Maps +22\n\n- 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.\n- 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.\n\n### Reliability: Woosmap +15\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Stadia Maps +10\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Stadia Maps +5\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Stadia Maps | Woosmap | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 78 | Woosmap +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 81 | Stadia Maps +5 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 76 | Stadia Maps +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 43 | Woosmap +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Stadia Maps +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 26 | Stadia Maps +54 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 76 | 54 | Stadia Maps +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.2 · B** | **59.4 · C** | |\n\n## Facts side by side\n\n| Fact | Stadia Maps | Woosmap |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Stadia Maps | WOOSMAP SAS |\n| Hosted endpoint | `https://api.stadiamaps.com` | `https://api.woosmap.com/mcp` |\n| Transports | HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| Price for geocoding | $0.40 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | BSD-3-Clause (MCP server) | none |\n| Tools exposed | 6 | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-26 | none |\n| Terms last updated | 2026-03-18 | no date given |\n| Privacy policy last updated | 2026-10-01 | 2024-07-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 23 stars, 6.1k npm/wk, 192 PyPI/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Stadia Maps\n\n- -0.3 on 8 October 2026: checklist\n\n### Woosmap\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Stadia Maps.** Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.\n\n**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.\n\n## Before you call either\n\n### Stadia Maps\n\n1. Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL\n2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough\n3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent\n4. Don't write geocodes to a database on Free or Starter\n5. Use bulk-geocode for addresses only, not POI names\n\n### Woosmap\n\n1. Send the private key in the X-Api-Key header, not the private_key query parameter\n2. Use a read-only private key for the MCP server unless the task writes stores or datasets\n3. On 429 wait the `t` seconds from the RateLimit header, retry at most three times, and pause batches when `r` reaches 0\n4. Use find_stores_nearby for the customer's own locations and find_nearby for public POIs\n5. Read endpoint parameters from the /api-reference/ Markdown pages, which llms.txt marks as authoritative\n\n## Questions\n\n### Which is better for AI agents, Stadia Maps or Woosmap?\n\nStadia 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.\n\n### Do Stadia Maps and Woosmap need an API key?\n\nBoth need an API key.\n\n### Can an agent call Stadia Maps and Woosmap without installing anything?\n\nYes. Stadia Maps has a hosted endpoint at https://api.stadiamaps.com and Woosmap at https://api.woosmap.com/mcp.\n\n\n## For agents\n\n- 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\n- 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`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/stadia-maps.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json\n\n## Other comparisons with Stadia Maps or Woosmap\n\n- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md)\n- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)\n- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)\n- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)\n- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)\n- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)\n- [Geocodio vs Stadia Maps](https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)\n- [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md)\n- [Google Maps Platform + Grounding Lite MCP vs Woosmap](https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.md)\n- [HERE Location Services vs Stadia Maps](https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md)\n- [HERE Location Services vs Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md)\n- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)\n- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md)\n- [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md)\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)\n- [Nominatim vs Stadia Maps](https://www.anchorterminal.com/compare/nominatim-vs-stadia-maps.md)\n- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-vs-woosmap.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Radar vs Woosmap](https://www.anchorterminal.com/compare/radar-vs-woosmap.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md)\n- [NextBillion.ai vs Stadia Maps](https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.md)\n- [NextBillion.ai vs Woosmap](https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Stadia Maps vs Woosmap", "url": "" } ], "description": "Stadia Maps scores 65.2 (B) to Woosmap's 59.4 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Stadia Maps B 65.2", "Woosmap C 59.4", "scores" ], "h1": "Stadia Maps vs Woosmap", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/stadia-maps-vs-woosmap", "published": "2026-10-01", "section": "tools", "title": "Stadia Maps vs Woosmap for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap" }, "tokens": { "markdown": 4150, "slim": 2280 }, "version": 1 }