{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/mapbox.json", "name": "Mapbox APIs + MCP", "score": 77.2, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "mapbox" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/amazon-location.json", "name": "Amazon Location Service", "score": 76.5, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "amazon-location" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/google-maps-platform.json", "name": "Google Maps Platform + Grounding Lite MCP", "score": 75.4, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "google-maps-platform" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/azure-maps.json", "name": "Azure Maps", "score": 67.1, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "azure-maps" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/arcgis.json", "name": "ArcGIS Location Platform", "score": 66.1, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "arcgis" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/stadia-maps.json", "name": "Stadia Maps", "score": 65.2, "shared": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "slug": "stadia-maps" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 78, "points": 15.6, "reason": "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.", "checked": "2026-11-06" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 81, "points": 13.16, "reason": "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.", "checked": "2026-11-06" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 76, "points": 12.35, "reason": "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.", "checked": "2026-11-06" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 43, "points": 7.53, "reason": "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.", "checked": "2026-11-06" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 30, "points": 3.75, "reason": "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.", "checked": "2026-11-06" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 26, "points": 2.28, "reason": "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.", "checked": "2026-11-06" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 54, "points": 4.72, "note": "editorial 31, provenance 76", "reason": "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.", "checked": "2026-11-06" } ], "assessment": { "date": "2026-11-06", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "llms.txt", "url": "https://developers.woosmap.com/llms.txt", "seen": "2026-11-06" }, { "what": "OpenAPI spec", "url": "https://developers.woosmap.com/assets/woosmap-openapi3.json", "seen": "2026-11-06" }, { "what": "authentication", "url": "https://developers.woosmap.com/api-reference/authentication.md", "seen": "2026-11-06" }, { "what": "rate limits", "url": "https://developers.woosmap.com/api-reference/rate-limits.md", "seen": "2026-11-06" }, { "what": "MCP server overview", "url": "https://developers.woosmap.com/products/mcp-server/overview.md", "seen": "2026-11-06" }, { "what": "MCP quick start", "url": "https://developers.woosmap.com/products/mcp-server/get-started.md", "seen": "2026-11-06" }, { "what": "pricing", "url": "https://www.woosmap.com/pricing", "seen": "2026-11-06" }, { "what": "online terms", "url": "https://www.woosmap.com/policies/terms-online", "seen": "2026-11-06" }, { "what": "legal notice", "url": "https://www.woosmap.com/policies/legal", "seen": "2026-11-06" }, { "what": "privacy policy", "url": "https://www.woosmap.com/policies/privacy", "seen": "2026-11-06" }, { "what": "status page", "url": "https://status.woosmap.com/", "seen": "2026-11-06" } ], "openQuestions": [ "unchecked: incident history beyond the 15 days on the status home page, since the history page loads by script and /api/ is disallowed by robots.txt", "unchecked: per-request prices on the Pro tiers, shown only in a script-driven calculator", "unchecked: storage and caching terms for geocoding results, which weren't found in the online terms", "unchecked: SDK versions and release dates on GitHub, because the GitHub API was rate-limited for us", "The MCP server's launch date and tool definitions aren't public, since it is closed and hosted", "A request to https://status.woosmap.com/api/v2/incidents.json, a path the status host's robots.txt disallows, was sent by mistake on 6 November 2026 before robots.txt was read. Its contents aren't used; the reliability line rests only on the status home page" ] }, "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 }, "scoreHistory": [ { "date": "2026-11-06", "grade": "C", "kind": "listed", "method": "0.7", "score": 59.4 } ] }, "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" }, "notable": [ "Hosted MCP server at https://api.woosmap.com/mcp with nine tools (geocode_address, reverse_geocode, find_nearby, find_stores_nearby, get_place_details, get_route, get_tolls, get_distance_matrix and create_static_map) (https://developers.woosmap.com/products/mcp-server/overview.md)", "OpenAPI 3.1 spec, version 1.46.3, with 47 paths (https://developers.woosmap.com/assets/woosmap-openapi3.json)", "Rate limits per endpoint with RateLimit-Policy and RateLimit headers and written 429 retry rules (https://developers.woosmap.com/api-reference/rate-limits.md)", "llms.txt is a routing index that marks the /api-reference/ pages as authoritative, with a Markdown twin of every page (https://developers.woosmap.com/llms.txt)", "The pricing page says the Address API is being deprecated for Pro Plan subscriptions in favour of Localities (https://www.woosmap.com/pricing)" ], "area": "everyday", "details": [ { "label": "Surface listed", "value": "The REST APIs at api.woosmap.com and the hosted MCP server at api.woosmap.com/mcp, read from developers.woosmap.com (llms.txt, OpenAPI spec, Markdown pages), the pricing, terms, legal and privacy pages and status.woosmap.com on 6 November 2026. No account was made, no key was used and no MCP session was opened" }, { "label": "APIs", "value": "Localities (autocomplete, geocode, details, postal codes), Stores search and data management, Distance (route, matrix, async matrix, tolls, isochrone), Geolocation, Indoor, Map and static maps, Transit and a what3words wrapper" }, { "label": "Rate limits", "value": "Set per endpoint and shared by a project's keys, shown on each reference page (for example 50 a second). RateLimit headers on every response" }, { "label": "MCP server", "value": "Hosted, closed source, nine tools over public POI data and the customer's own stores, connected through mcp-remote with a private key header" }, { "label": "Plans", "value": "Free up to 10,000 requests a month, Pro on public tiers, Enterprise by quote with a 99.9% SLA" }, { "label": "Legal entity", "value": "WOOSMAP SAS, 5 rue du Plan du Palais, Montpellier, France, RCS Montpellier 983 770 405, with the Commercial Court of Paris named for disputes" } ], "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, "checks": [ { "check": "Legal entity named", "value": "WOOSMAP SAS", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "woosmap.com, registered 2010-06-04 (16 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "api.woosmap.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects", "points": 8.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 3 of the 8 things a reader expects", "points": 6.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.woosmap.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "2 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "a support address, help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.woosmap.com/policies/terms-online", "state": "read", "readAt": "2026-11-06", "words": 15033, "points": 8.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "25.2 The Commercial Court of Paris (“Tribunal de Commerce de Paris”) shall have exclusive jurisdiction to hear any dispute arising out of or in connection with the interpretation and/or performance of these Online TOS, however, the Parties acknowledge and agree that in the event that the subject matter of any such dis…", "says": "Disputes go to the courts of Paris" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "…total liability, in case of “Transit API” service use, under this agreement shall be limited to the amount paid by the Client for the ”Transit API” service during the twelve (12) months preceding the claim.", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "In such a case, the sole right and remedy of the Client will thus be to terminate these Online TOS by providing a written notice of termination to the Service Provider in the conditions set out in Section 17.1 of the General Terms." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "For example, Customer will not create multiple billing accounts or Projects to avoid incurring fees, prevent Woosmap from accurately calculating Customer’s Service usage levels or abuse any free Service quotas." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "The Client acknowledges that the “Transit API” service may be subject to limitations inherited from the “Public Transit API” provided by Here Technologies or managed by Woosmap, such as the number of query per second (see Woosmap dev doc), or any Service Level Agreement associated with the Here Technologies service." } ] }, { "kind": "privacy", "url": "https://www.woosmap.com/policies/privacy", "state": "read", "readAt": "2026-11-06", "statedDate": "2024-07-01", "words": 1161, "points": 6.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Effective:July 01, 2024", "says": "Last updated 2024-07-01" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "We may collect the following information when you create an account to the Woosmap Platform or use any contact form available in the website:" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": false }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": false }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": false }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": false }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "To exercise any of these rights, please contact us at [email protected] or postal mail to Woosmap, 5 rue du Plan du Palais, 34000 Montpellier (FRANCE).", "says": "Gives an email address, hidden from our reader by the page" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": false } ] } ] }, "humans": { "slug": "woosmap", "checked": "2026-11-06", "company": "Woosmap", "people": [ { "name": "Jean-Thomas Rouzin", "role": "Co-founder and Chief Executive Officer", "founder": true, "page": "/people/jean-thomas-rouzin/" }, { "name": "Mathias Fliti", "role": "Co-founder, Web Geo Services (the company that built Woosmap)", "founder": true, "page": "/people/mathias-fliti/" } ], "peopleNote": "Woosmap's online terms, read on 6 November 2026, name Jean-Thomas Rouzin as Chief Executive Officer, and Woosmap's own news page on his BSmart TV interview calls him cofondateur (co-founder) and PDG. Private Equity Wire's report of 30 June 2021 says Web Geo Services, founded in 2009 in Montpellier, built its own platform Woosmap and was led by its two founders, Mathias Fliti and Jean-Thomas Rouzin; Mathias Fliti's present role isn't stated on the pages read. No personal accounts are linked. Datasharp's home page lists Woosmap as one of its four group companies, in the group since 2025, with a quote from JT Rouzin, and says Datasharp is backed by the private equity firm Strada Partners. Le Monde du Droit's deal note of 4 December 2025 says the law firm Racine advised Datasharp on its acquisition of Woosmap. The legal page now names Woosmap, an SAS in Montpellier (SIREN 983 770 405). No price was disclosed, so there is no valuation, and CFNEWS's report of the sale is behind a paywall and wasn't read. Before the sale, CAPZA (CAPZA Growth Tech) took a majority stake in Web Geo Services in June 2021 alongside IRDI Capital Investissement, a historical shareholder that reinvested; Seventure Partners and Paris Region Venture Fund (managed by Karista) exited fully then, so they are left out. No source read says whether CAPZA and IRDI kept a stake through the Datasharp deal. No total raised is stated.", "companySocial": { "linkedin": "https://www.linkedin.com/company/woosmap/", "x": "https://x.com/woosmap" }, "support": { "emails": [ "support@woosmap.com" ], "urls": [ "https://developers.woosmap.com/" ] }, "sources": [ "https://www.woosmap.com/policies/terms-online", "https://www.woosmap.com/policies/legal", "https://www.woosmap.com/company", "https://developers.woosmap.com/api-reference/rate-limits.md", "https://www.woosmap.com/fr/actualites/interview-bsmart-tv", "https://privateequitywire.com/news/capza-growth-tech-acquires-majority-stake-web-geo-services", "https://www.datasharp.com/", "https://www.lemondedudroit.fr/deals/101906-racine-accompagne-datasharp-acquisition-woosmap.html" ], "ownership": { "status": "acquired", "parent": "Datasharp", "acquiredBy": "Datasharp", "acquiredDate": "2025", "checked": "2026-11-06", "sources": [ "https://www.datasharp.com/", "https://www.lemondedudroit.fr/deals/101906-racine-accompagne-datasharp-acquisition-woosmap.html", "https://www.woosmap.com/policies/legal" ] }, "investors": [ { "name": "CAPZA", "kind": "vc", "rounds": [ "Majority stake in Web Geo Services, June 2021" ], "lead": true, "source": "https://privateequitywire.com/news/capza-growth-tech-acquires-majority-stake-web-geo-services", "quote": "CAPZA has acquired a majority stake in Web Geo Services, a French API platform publisher", "page": "/investors/capza/" }, { "name": "IRDI Capital Investissement", "kind": "vc", "rounds": [ "Majority stake in Web Geo Services, June 2021" ], "url": "https://www.irdi.fr", "source": "https://privateequitywire.com/news/capza-growth-tech-acquires-majority-stake-web-geo-services", "quote": "alongside IRDI Capital Investissement, an investment fund based in southwest of France and historical shareholder of the company, which has decided to reinvest in the operation", "page": "/investors/irdi-capital-investissement/" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/woosmap.json", "live": { "slug": "woosmap", "probe": { "target": "https://api.woosmap.com/mcp", "method": "get", "lastAt": "2026-11-07T17:50:16.626951023Z", "lastOk": true, "lastStatus": 401, "lastMs": 57, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 48, "p95ms24h": 118, "samples24h": 195, "samples30d": 195, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 182, "ok": 182 } ] }, "vendorStatus": { "page": "https://status.woosmap.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T17:46:29.862821134Z" }, "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-07T17:50:16.626951023Z" } }, "verify": { "accepts": "a page on woosmap.com or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/woosmap.svg", "body": { "slug": "woosmap", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/woosmap", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/woosmap\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/woosmap.svg\" alt=\"Woosmap on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Woosmap on Anchor Terminal](https://www.anchorterminal.com/badges/woosmap.svg)](https://www.anchorterminal.com/tools/woosmap)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/woosmap\"\u003eWoosmap on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/woosmap", "json": "https://www.anchorterminal.com/tools/woosmap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/woosmap.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/woosmap#pricing", "reviews": "https://www.anchorterminal.com/tools/woosmap#reviews", "slim": "https://www.anchorterminal.com/tools/woosmap.min.md" }, "markdown": "## Overview\n\n**Grade C · 59.4/100 · rank #704 of 1486 · #12 in Maps, geocoding \u0026 places · not agent-ready · confidence medium**\n\n\n## Assessment\n\nWoosmap 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | WOOSMAP SAS (https://www.woosmap.com) |\n| Kind | HTTP API |\n| Category | Maps, geocoding \u0026 places (https://www.anchorterminal.com/categories/maps) |\n| Transport | HTTP, Streamable HTTP |\n| Endpoint | `https://api.woosmap.com/mcp` |\n| Auth | API key · 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. |\n| Pricing | Freemium (Freemium) · 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. |\n| x402 | No · 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. |\n| Licence | unknown |\n| Tools exposed | 9 |\n| Docs | https://developers.woosmap.com/ |\n| llms.txt | https://developers.woosmap.com/llms.txt |\n| Surface listed | The REST APIs at api.woosmap.com and the hosted MCP server at api.woosmap.com/mcp, read from developers.woosmap.com (llms.txt, OpenAPI spec, Markdown pages), the pricing, terms, legal and privacy pages and status.woosmap.com on 6 November 2026. No account was made, no key was used and no MCP session was opened |\n| APIs | Localities (autocomplete, geocode, details, postal codes), Stores search and data management, Distance (route, matrix, async matrix, tolls, isochrone), Geolocation, Indoor, Map and static maps, Transit and a what3words wrapper |\n| Rate limits | Set per endpoint and shared by a project's keys, shown on each reference page (for example 50 a second). RateLimit headers on every response |\n| MCP server | Hosted, closed source, nine tools over public POI data and the customer's own stores, connected through mcp-remote with a private key header |\n| Plans | Free up to 10,000 requests a month, Pro on public tiers, Enterprise by quote with a 99.9% SLA |\n| Legal entity | WOOSMAP SAS, 5 rue du Plan du Palais, Montpellier, France, RCS Montpellier 983 770 405, with the Commercial Court of Paris named for disputes |\n| Capabilities | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles |\n| 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 |\n| JSON | https://www.anchorterminal.com/api/v1/tools/woosmap.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 78 | 15.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 81 | 13.2 |\n| Agent ergonomics | 13% | 16.2 | 76 | 12.3 |\n| Security \u0026 auth | 14% | 17.5 | 43 | 7.5 |\n| Payments \u0026 pricing | 10% | 12.5 | 30 | 3.8 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 26 | 2.3 |\n| Transparency \u0026 trust (editorial 31, provenance 76) | 7% | 8.8 | 54 | 4.7 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **59.4 → C** |\n\n### Why each score\n\n- Reliability 78 (checked 2026-11-06): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 81 (checked 2026-11-06): 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- Agent ergonomics 76 (checked 2026-11-06): 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.\n- Security \u0026 auth 43 (checked 2026-11-06): 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.\n- Payments \u0026 pricing 30 (checked 2026-11-06): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 26 (checked 2026-11-06): 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- Transparency \u0026 trust 54 (checked 2026-11-06): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (18 items). What it covers is at https://www.anchorterminal.com/fixes/woosmap.md (JSON https://www.anchorterminal.com/fixes/woosmap.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"woosmap\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: incident history beyond the 15 days on the status home page, since the history page loads by script and /api/ is disallowed by robots.txt\n- unchecked: per-request prices on the Pro tiers, shown only in a script-driven calculator\n- unchecked: storage and caching terms for geocoding results, which weren't found in the online terms\n- unchecked: SDK versions and release dates on GitHub, because the GitHub API was rate-limited for us\n- The MCP server's launch date and tool definitions aren't public, since it is closed and hosted\n- A request to https://status.woosmap.com/api/v2/incidents.json, a path the status host's robots.txt disallows, was sent by mistake on 6 November 2026 before robots.txt was read. Its contents aren't used; the reliability line rests only on the status home page\n\n### Sources\n\n- llms.txt: \u003chttps://developers.woosmap.com/llms.txt\u003e (seen 2026-11-06)\n- OpenAPI spec: \u003chttps://developers.woosmap.com/assets/woosmap-openapi3.json\u003e (seen 2026-11-06)\n- authentication: \u003chttps://developers.woosmap.com/api-reference/authentication.md\u003e (seen 2026-11-06)\n- rate limits: \u003chttps://developers.woosmap.com/api-reference/rate-limits.md\u003e (seen 2026-11-06)\n- MCP server overview: \u003chttps://developers.woosmap.com/products/mcp-server/overview.md\u003e (seen 2026-11-06)\n- MCP quick start: \u003chttps://developers.woosmap.com/products/mcp-server/get-started.md\u003e (seen 2026-11-06)\n- pricing: \u003chttps://www.woosmap.com/pricing\u003e (seen 2026-11-06)\n- online terms: \u003chttps://www.woosmap.com/policies/terms-online\u003e (seen 2026-11-06)\n- legal notice: \u003chttps://www.woosmap.com/policies/legal\u003e (seen 2026-11-06)\n- privacy policy: \u003chttps://www.woosmap.com/policies/privacy\u003e (seen 2026-11-06)\n- status page: \u003chttps://status.woosmap.com/\u003e (seen 2026-11-06)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/woosmap/history.json\n\n- 2026-11-06: graded 59.4 C (methodology 0.7)\n\n## Who's behind it (provenance 76/100, checked 2026-11-06)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | WOOSMAP SAS | 20/20 |\n| Domain age | woosmap.com, registered 2010-06-04 (16 years) | 15/15 |\n| Endpoint on the vendor's domain | api.woosmap.com | 15/15 |\n| Terms of service | read, states 5 of the 7 things a reader expects | 8.3/10 |\n| Privacy policy | read, states 3 of the 8 things a reader expects | 6.3/10 |\n| Status page | status.woosmap.com | 10/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n| People named | 2 named with their role, none with a public profile | 7/10 |\n| Support route | a support address, help pages | 5/5 |\n\nThe 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.\n\nstatus.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.\n\nwww.woosmap.com/.well-known/security.txt returns 404.\n\nNo public API changelog was found. developers.woosmap.com/changelog/ and /release-notes/ return 404.\n\nRDAP 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.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.woosmap.com/policies/terms-online), read 2026-11-06, gives no date, states 5 of the 7 things a reader expects.\n\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. Disputes go to the courts of Paris.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Not found in the text. Says how changes to the terms are announced.\n\n**Privacy policy** (https://www.woosmap.com/policies/privacy), read 2026-11-06, dated 2024-07-01, states 3 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2024-07-01.\n- Not found in the text. Says how long data is kept.\n- Not found in the text. Says who else receives the data.\n- Not found in the text. Says whether personal data is sold or shared for advertising.\n- Not found in the text. Says what rights people have over their data.\n- Gives a privacy contact. Gives an email address, hidden from our reader by the page.\n- Not found in the text. Says where data is transferred or stored.\n\n## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)\n\n### Key people\n\n- Jean-Thomas Rouzin, Co-founder and Chief Executive Officer\n- Mathias Fliti, Co-founder, Web Geo Services (the company that built Woosmap)\n- Note: Woosmap's online terms, read on 6 November 2026, name Jean-Thomas Rouzin as Chief Executive Officer, and Woosmap's own news page on his BSmart TV interview calls him cofondateur (co-founder) and PDG. Private Equity Wire's report of 30 June 2021 says Web Geo Services, founded in 2009 in Montpellier, built its own platform Woosmap and was led by its two founders, Mathias Fliti and Jean-Thomas Rouzin; Mathias Fliti's present role isn't stated on the pages read. No personal accounts are linked. Datasharp's home page lists Woosmap as one of its four group companies, in the group since 2025, with a quote from JT Rouzin, and says Datasharp is backed by the private equity firm Strada Partners. Le Monde du Droit's deal note of 4 December 2025 says the law firm Racine advised Datasharp on its acquisition of Woosmap. The legal page now names Woosmap, an SAS in Montpellier (SIREN 983 770 405). No price was disclosed, so there is no valuation, and CFNEWS's report of the sale is behind a paywall and wasn't read. Before the sale, CAPZA (CAPZA Growth Tech) took a majority stake in Web Geo Services in June 2021 alongside IRDI Capital Investissement, a historical shareholder that reinvested; Seventure Partners and Paris Region Venture Fund (managed by Karista) exited fully then, so they are left out. No source read says whether CAPZA and IRDI kept a stake through the Datasharp deal. No total raised is stated.\n- Woosmap: LinkedIn https://www.linkedin.com/company/woosmap/ X https://x.com/woosmap\n\n### Ownership and investors\n\n- Ownership: Acquired by Datasharp, 2025\n- Backed by: CAPZA, IRDI Capital Investissement\n\n### Getting support\n\n- Support email: support@woosmap.com\n- Help: https://developers.woosmap.com/\n- Sources: https://www.woosmap.com/policies/terms-online, https://www.woosmap.com/policies/legal, https://www.woosmap.com/company, https://developers.woosmap.com/api-reference/rate-limits.md, https://www.woosmap.com/fr/actualites/interview-bsmart-tv, https://privateequitywire.com/news/capza-growth-tech-acquires-majority-stake-web-geo-services, https://www.datasharp.com/, https://www.lemondedudroit.fr/deals/101906-racine-accompagne-datasharp-acquisition-woosmap.html\n\n## Live (updated 2026-11-07 17:50 UTC)\n\n- Right now: up, HTTP 401, 57 ms, checked 2026-11-07 17:50 UTC (get on `https://api.woosmap.com/mcp`, asks for auth)\n- Uptime 24h 100.0% (195 probes) · 30 days 100.0% (195 probes) · p50 48 ms · p95 118 ms\n- Vendor status page: no problems reported, All Systems Operational\n- security.txt: none\n- Watching privacy \u003chttps://www.woosmap.com/policies/privacy\u003e\n- Watching terms \u003chttps://www.woosmap.com/policies/terms-online\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/woosmap.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- OpenAPI 3.1 spec with 47 paths, llms.txt routing index and Markdown twins of every page\n- Per-endpoint rate limits with RateLimit headers and explicit 429 retry rules and sample code\n- Hosted MCP server at api.woosmap.com/mcp with nine tools, including search over the customer's own store data\n- Read-only and read/write private keys with IP, iOS or Android restrictions and an X-Api-Key header\n- Free plan of 10,000 requests a month with no card\n\n## Weaknesses\n\n- No public changelog or release notes for the APIs\n- No security.txt, disclosure policy or certification found\n- The privacy policy covers the website only, with nothing on API data retention\n- Per-request prices aren't readable without the script-driven calculator\n- `private_key` in the query string is documented and is the spec's default scheme\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl -H \"X-Api-Key: $WOOSMAP_PRIVATE_KEY\" \"https://api.woosmap.com/localities/geocode?address=Place+de+la+Comedie+Montpellier\"\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"woosmap\": {\n \"args\": [\n \"mcp-remote\",\n \"https://api.woosmap.com/mcp\",\n \"--header\",\n \"X-Api-Key: PRIVATE_KEY\"\n ],\n \"command\": \"npx\"\n }\n }\n}\n```\n\nThrough letme: https://letme.dev/woosmap. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Mapbox APIs + MCP | BB | 77.2 | 35 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md |\n| Amazon Location Service | BB | 76.5 | 43 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/amazon-location.md |\n| Google Maps Platform + Grounding Lite MCP | BB | 75.4 | 63 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md |\n| Azure Maps | B | 67.1 | 338 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md |\n| ArcGIS Location Platform | B | 66.1 | 380 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md |\n| Stadia Maps | B | 65.2 | 431 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Hosted MCP server at https://api.woosmap.com/mcp with nine tools (geocode_address, reverse_geocode, find_nearby, find_stores_nearby, get_place_details, get_route, get_tolls, get_distance_matrix and create_static_map) (source: \u003chttps://developers.woosmap.com/products/mcp-server/overview.md\u003e)\n- OpenAPI 3.1 spec, version 1.46.3, with 47 paths (source: \u003chttps://developers.woosmap.com/assets/woosmap-openapi3.json\u003e)\n- Rate limits per endpoint with RateLimit-Policy and RateLimit headers and written 429 retry rules (source: \u003chttps://developers.woosmap.com/api-reference/rate-limits.md\u003e)\n- llms.txt is a routing index that marks the /api-reference/ pages as authoritative, with a Markdown twin of every page (source: \u003chttps://developers.woosmap.com/llms.txt\u003e)\n- The pricing page says the Address API is being deprecated for Pro Plan subscriptions in favour of Localities (source: \u003chttps://www.woosmap.com/pricing\u003e)\n\n- #12 of 18 in 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## Compare\n\n- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md): BB 76.5 vs C 59.4\n- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md): B 66.1 vs C 59.4\n- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md): B 67.1 vs C 59.4\n- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md): C 58.1 vs C 59.4\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md): BB 72.2 vs C 59.4\n- [Google Maps Platform + Grounding Lite MCP vs Woosmap](https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.md): BB 75.4 vs C 59.4\n- [HERE Location Services vs Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md): C 58.4 vs C 59.4\n- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md): C 60.3 vs C 59.4\n- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md): BB 77.2 vs C 59.4\n- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md): F 35.4 vs C 59.4\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md): B 62.1 vs C 59.4\n- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md): B 63.5 vs C 59.4\n- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-vs-woosmap.md): B 67.5 vs C 59.4\n- [Radar vs Woosmap](https://www.anchorterminal.com/compare/radar-vs-woosmap.md): D 53.3 vs C 59.4\n- [Stadia Maps vs Woosmap](https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md): B 65.2 vs C 59.4\n- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md): E 45.9 vs C 59.4\n- [NextBillion.ai vs Woosmap](https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md): C 55.4 vs C 59.4\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on woosmap.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"woosmap\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/woosmap\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/woosmap.svg\" alt=\"Woosmap on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Woosmap on Anchor Terminal](https://www.anchorterminal.com/badges/woosmap.svg)](https://www.anchorterminal.com/tools/woosmap)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/woosmap\"\u003eWoosmap on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Woosmap is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/woosmap-dark.png\n- Light: https://www.anchorterminal.com/assets/share/woosmap-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Maps, geocoding \u0026 places", "url": "https://www.anchorterminal.com/categories/maps" }, { "name": "Woosmap", "url": "" } ], "description": "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.", "facts": [ "rank #704 of 1486", "API key auth", "0 desk reviews" ], "h1": "Woosmap", "image": "https://www.anchorterminal.com/assets/og/tools-woosmap.png", "path": "/tools/woosmap", "published": "2026-10-01", "section": "tools", "title": "Woosmap review (2026): pricing, alternatives and grade C", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/tools/woosmap" }, "tokens": { "markdown": 6750, "slim": 1430 }, "version": 1 }