{ "data": { "a": { "slug": "here-location-services", "name": "HERE Location Services", "vendor": "HERE Technologies", "vendorUrl": "https://www.here.com", "kind": "http-api", "category": "maps", "summary": "HERE Technologies' REST APIs for geocoding, place search, routing, matrix and isoline routing, traffic, transit and map tiles, called with an API key or OAuth token. A hosted MCP server, HERE Location Reasoning, exposes 13 of these operations as tools.", "url": "https://www.anchorterminal.com/tools/here-location-services", "markdownUrl": "https://www.anchorterminal.com/tools/here-location-services.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/here-location-services.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/here-location-services.json", "dns": "here-location-services.grade.anchorterminal.com", "license": "Proprietary service under the HERE Platform Terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://geocode.search.hereapi.com/v1", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A HERE platform account, created in a browser with email verification, lets a person register an app and create up to two API keys, OAuth 2.0 credentials or OAuth 2.1 `private_key_jwt` credentials. REST calls take the key as the `apiKey` query parameter or a bearer token from https://account.api.here.com/oauth2/token. Location Reasoning needs a bearer token on `tools/call` and an account entitlement, and returns 403 without one.", "pricing": "freemium", "pricingNotes": "HERE's docs say a new organisation can get started for free on the Base Plan. The price table at here.com/get-started/pricing is drawn by script and was not read, so no allowance or per-request price is quoted. Support plans run from $50 a month (Developer). Location Reasoning is also sold through AWS Marketplace (checked 2026-10-09).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.here.com", "llmsTxt": "https://docs.here.com/llms.txt", "openapi": "https://docs.here.com/geocoding-and-search/reference/get_geocode.md", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "openapi", "llms-txt", "oauth", "free-tier", "enterprise", "eu", "sla", "closed-source" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 58.4, "grade": "C", "agentReady": false, "rank": 753, "ranked": true, "rankOf": 1510, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 93, "maintenance": 45, "payments": 0, "reliability": 55, "schema": 89, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": -3, "negativeNotes": [ "10 July 2026. The Routing v8 changelog marks `mlDuration` as Deprecated and says `return=mlDuration` is still accepted but no longer returns a value. HERE's lifecycle policy says a deprecated feature continues to operate for 6 to 12 months after notice. Three points (https://docs.here.com/routing/docs/routing-v8-changelog.md)" ], "verdict": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. No numeric rate limit or retry guidance was found, prices were unreadable, and HERE's terms bar using its materials with an AI system and bar scraping, so its pages could not be re-read.", "bestFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "strengths": [ "Every endpoint page has a Markdown twin holding its OpenAPI 3.0 definition, indexed from `llms.txt` files per product", "99.9 per cent monthly availability targets published for Geocoding and Search v7 and Routing v8", "Lifecycle policy promises six months' notice before a product is discontinued and 6 to 12 months for a deprecated feature", "OAuth 2.1 `private_key_jwt` credentials alongside API keys, with two keys an app for rotation and trusted-domain limits", "ISO 27001, 27701, 27017, 27018 and 42001 certificates, TISAX AL3, and SOC 2 Type 2 for Platform Foundation and Workspace" ], "weaknesses": [ "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run", "The Base Plan price table is drawn by script, so per-request prices, free allowances and rate limits were not read", "API keys travel in the `apiKey` query parameter", "Results may be cached or stored outside the platform for 30 days at most, and only as HTTP caching headers allow", "Location Reasoning returns 403 unless the account is entitled, and the docs send the reader to an account representative or AWS Marketplace", "The acceptable use policy of January 2022 lists benchmarking, scraping and data mining among prohibited uses of HERE Materials, websites included" ], "agentNotes": [ "Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL", "Do not store results for more than 30 days, and follow the HTTP caching headers on each response", "Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota", "Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support", "For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.4 } ], "editorialScores": { "ergonomics": 93, "maintenance": 45, "payments": 0, "reliability": 55, "schema": 89, "security": 65, "transparency": 52 }, "provenanceScore": 73, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston\u0026limit=4\u0026apiKey=$HERE_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/here-location-services" }, "area": "everyday", "provenance": { "legalEntity": "HERE Europe B.V.", "domain": "here.com", "domainRegistered": "1995-06-11", "endpointOnVendorDomain": false, "terms": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "privacy": "https://www.here.com/en-gb/privacy", "statusPage": "https://status.here.com/status", "changelog": "https://docs.here.com/routing/docs/routing-v8-changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The HERE Platform Terms, effective 18 September 2023, name HERE Europe B.V., Kennedyplein 222-226, 5611 ZT Eindhoven, as contracting party, and HERE North America, LLC, Chicago, for customers in the Americas.", "The privacy policy, effective 29 August 2024, names HERE Global B.V. as controller and says it does not apply to personal data processed on behalf of customers. The Platform Terms incorporate it and a Data Processing Agreement published as a PDF.", "The APIs answer on hereapi.com (for example geocode.search.hereapi.com and router.hereapi.com) and the MCP server on hlr.here.ai, both second domains of the vendor.", "www.here.com/.well-known/security.txt returned the site's error page. The security page gives security@here.com and a 90-day disclosure window.", "RDAP for here.com gives a registration date of 1995-06-11.", "legal.here.com/en-gb/terms/here-platform redirects to the September 2023 terms on www.here.com." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/here-location-services.json", "live": { "slug": "here-location-services", "probe": { "target": "https://geocode.search.hereapi.com/v1", "method": "get", "lastAt": "2026-11-07T22:56:01.425067593Z", "lastOk": true, "lastStatus": 404, "lastMs": 146, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 136, "p95ms24h": 220, "samples24h": 244, "samples30d": 7251, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "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": 247 }, { "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": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.here.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:54.513837106Z" }, "securityTxt": { "url": "https://here.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:38.375401065Z" }, "llmsTxt": { "url": "https://docs.here.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:41.618757298Z" }, "domain": { "domain": "here.com", "registered": "1995-06-11", "source": "https://rdap.verisign.com/com/v1/domain/here.com", "checkedAt": "2026-11-01T14:19:40.338365968Z" }, "pages": [ { "url": "https://docs.here.com/routing/docs/routing-v8-changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:33.22290386Z", "changedAt": "2026-11-06T13:28:56.804164156Z", "fingerprint": "41722ae10c3c" }, { "url": "https://www.here.com/en-gb/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:29:44.517212853Z", "changedAt": "2026-10-27T04:01:29.602111544Z", "fingerprint": "a34c0fdaf19e" }, { "url": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023", "kind": "terms", "status": 404, "checkedAt": "2026-11-07T14:29:46.565606645Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "466d77d5e000" } ], "updatedAt": "2026-11-07T22:56:01.425067593Z" } }, "answer": "Woosmap scores 59.4 (C) on agent readiness against HERE Location Services's 58.4 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "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": 707, "ranked": true, "rankOf": 1510, "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-07T22:56:31.290273573Z", "lastOk": true, "lastStatus": 401, "lastMs": 50, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 50, "p95ms24h": 132, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.woosmap.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:57:54.387981929Z" }, "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-07T22:57:54.387981929Z" } }, "edges": [ { "by": 30, "category": "payments", "leads": "woosmap", "name": "Payments \u0026 pricing", "reasons": { "a": "Readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). No x402, MPP or L402 was found in the docs index or the terms (0). The Base Plan price page is public, but its table is drawn by script and showed no prices to our reader, so per-request prices score as absent, a limit of our reading and not a finding that prices are hidden (0). HERE's docs say a new organisation can get started for free, but whether a card is asked for was not established, so the free-tier line can't be credited (0; the 10 carried isn't a checklist value). Sign-up is a browser flow with email verification (0). Support plans are priced in public, from $50 a month for the Developer plan. 0+0+0+0 = 0.", "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": 0, "b": 30 } }, { "by": 23, "category": "reliability", "leads": "woosmap", "name": "Reliability", "reasons": { "a": "Graded on the REST APIs (Geocoding and Search v7, Routing v8) with the hosted lines. HERE's acceptable use policy bars data mining and scraping of HERE Materials, websites included, so HERE's hosts were not requested on 4 November and the 9 October readings stand. HERE's docs describe a public status page at status.here.com/status with current status, a status history tab and scheduled maintenance (per the 9 October check, not re-read on 4 November) (20). The page was drawn by script on 9 October and is now paused, so the record from 6 August is unread (5). No rate limit with a number was found in the docs; the Base Plan limits sit on a price page drawn by script (0; the 5 carried isn't a checklist value). The Limits and Quotas page says an exceeded quota returns 429 or 503 and that a surge can be throttled for about 10 minutes, and the OpenAPI definition lists 429, with no Retry-After header or backoff guidance and only reads involved (per the 9 October check, not re-read on 4 November). Documented 429 handling without backoff guidance reads at the line's 10 (the 7 carried isn't a checklist value). Monthly availability targets of 99.9 per cent are published for Geocoding and Search v7 and Routing v8, with service credits for the Essential support plan and above (per the 9 October check, not re-read on 4 November) (10). Both APIs are in the Active lifecycle stage (10). 20+5+0+10+10+10 = 55.", "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": 55, "b": 78 } }, { "by": 22, "category": "security", "leads": "here-location-services", "name": "Security \u0026 auth", "reasons": { "a": "All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). Credentials are API keys, OAuth 2.0 client credentials and OAuth 2.1 `private_key_jwt` with a registered JWK, where the private key stays with the customer. Tokens are short-lived and can be scoped to a project, and an app holds two API keys or two JWKs for rotation (30). Less 10 because the documented API key method is the `apiKey` query parameter (20). The location services only read. Trusted domains limit where a key works, and app credentials do not inherit the user's permissions (15 of 20). Results carry place names from third-party sources. The Location Reasoning examples load a `guardrails://location-reasoning-usage-policy` resource and a `hlr___secure_location_reasoning` prompt, whose text was not read (7 of 15). A Usage API reports billable usage by app and project. Per-call logs were not found (6 of 15). ISO/IEC 27001:2022, 27701, 27017, 27018 and 42001 certificates, SOC 2 Type 2 scoped to Platform Foundation and Workspace, TISAX AL3 and CSA STAR Level 2 are listed. A disclosure policy of 13 July 2023 names security@here.com with a 90-day window. No bug bounty and no security.txt were found (17 of 20). Total 65.", "b": "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." }, "scores": { "a": 65, "b": 43 } }, { "by": 19, "category": "maintenance", "leads": "here-location-services", "name": "Maintenance \u0026 community", "reasons": { "a": "HERE's changelogs sit on docs.here.com, paused under the acceptable use policy, so entries after 9 October are unread. On the 9 October reading the newest dated entries are Matrix Routing 8.49.0 on 9 September 2026 (a documentation change) and Routing 8.162.0 on 7 September 2026, 58 days before this check (20). From 6 August only Routing 8.161.0 (11 August) and 8.162.0 (7 September) fall in the window, with the Matrix documentation change at half, 2.5 in all and short of three (0, cause time; 8.160.0 of 16 July has left the window). Changelogs are public for each API, and paid support plans state response times from 72 hours down to 4 (10 of 15). HERE's GitHub repositories, read as a third-party host, show the HERE SDK for Android, iOS and Flutter current, with example apps tagged for releases 4.27.2.0 (17 August), 4.27.3.0 (3 September), 4.28.0.0 (1 October) and 4.28.1.0 (2 November 2026), and their search and routing engines are the SDKs the ergonomics note credits. The Python client for the REST APIs has carried a deprecation notice since 5 September 2023. These SDK releases aren't counted on the release lines, because their release notes sit on HERE's paused pages and nothing read shows them changing the location services (15; the 5 carried isn't a checklist value). Package health isn't visible for a closed service, and the SDK examples repository has no CI workflow (0; the 5 carried isn't a checklist value). 20+0+10+15+0 = 45.", "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": 45, "b": 26 } }, { "by": 17, "category": "ergonomics", "leads": "here-location-services", "name": "Agent ergonomics", "reasons": { "a": "All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). `limit` sizes geocoding responses (1 to 100, default 20), and `show` and `return` parameters add optional blocks only when asked for. The MCP server lists 13 tools, two of them experimental, and passes cached route and isoline IDs between tools so geometry is not returned twice (18 of 25). Filters by country, result type, position and bounding area and a result limit are documented, with no offset or cursor paging for geocoding (20; the 15 carried isn't a checklist value, and filters with a size limit meet the line). Errors carry `status`, `title`, `code`, `cause`, `action` and `correlationId`, and the routing changelog names error codes such as `E605502` (20; the 17 carried isn't a checklist value). The location calls are reads and safe to repeat (20; the 14 carried isn't a checklist value; MCP annotations were not read). A geocode needs only `q` and a credential, and HERE publishes SDKs in JavaScript, Android, iOS and Flutter, for maps rather than as REST clients (15; the 10 carried isn't a checklist value). 18+20+20+20+15 = 93.", "b": "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." }, "scores": { "a": 93, "b": 76 } }, { "by": 9, "category": "transparency", "leads": "here-location-services", "name": "Transparency \u0026 trust", "reasons": { "a": "All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). Closed service under public, dated terms. The HERE Platform Terms, effective 18 September 2023, name the contracting entity by region and govern the Base Plan (15 of 30). The terms say HERE analyses use of the platform and uses anonymised or aggregated findings to develop its products, and Essential Data Processing domains switch that off. The privacy policy of 29 August 2024 says it does not cover processing done on behalf of customers and gives no retention periods. The DPA is a PDF we did not read (14 of 30). The Product Lifecycle Policy gives six months' notice before discontinuation and 6 to 12 months for a deprecated feature, and changelogs mark deprecations with dates (20). No sub-processor list or data location was found on the pages read (3 of 20). Total 52.", "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": 63, "b": 54 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HERE Technologies", "b": "WOOSMAP SAS", "name": "Vendor" }, { "a": "https://geocode.search.hereapi.com/v1", "b": "https://api.woosmap.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the HERE Platform Terms", "b": "none", "name": "Licence" }, { "a": "13", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-09", "b": "none", "name": "Last release" }, { "a": "2023-09-18", "b": "no date given", "name": "Terms last updated" }, { "a": "2024-08-29", "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": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "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" } ], "faq": [ { "answer": "Woosmap scores 59.4 (C) on agent readiness against HERE Location Services's 58.4 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, HERE Location Services or Woosmap?" }, { "answer": "HERE Location Services takes an API key or an OAuth sign-in. Woosmap needs an API key.", "question": "Do HERE Location Services and Woosmap need an API key?" }, { "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Woosmap at https://api.woosmap.com/mcp.", "question": "Can an agent call HERE Location Services and Woosmap without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 89 against 81", "Agent ergonomics, 93 against 76", "Security \u0026 auth, 65 against 43", "Maintenance \u0026 community, 45 against 26", "Transparency \u0026 trust, 63 against 54" ], "also": null, "goodFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.", "slug": "here-location-services", "watchFor": "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run" }, { "aheadOn": [ "Reliability, 78 against 55", "Payments \u0026 pricing, 30 against 0" ], "also": [ "Free to start without a card", "No incidents deducted, where HERE Location Services loses 3 points for them" ], "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": { "here-location-services": [ { "causes": [ "correction", "time" ], "date": "2026-11-04", "delta": 0.4, "from": 58, "fromGrade": "C", "to": 58.4, "toGrade": "C" } ], "woosmap": null }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.json", "title": "Amazon Location Service vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services" }, { "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-here-location-services.json", "title": "ArcGIS Location Platform vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services" }, { "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-here-location-services.json", "title": "Azure Maps vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services" }, { "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-here-location-services.json", "title": "Geoapify Location Platform + MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services" }, { "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-here-location-services.json", "title": "Geocodio vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geocodio-vs-here-location-services" }, { "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-here-location-services.json", "title": "Google Maps Platform + Grounding Lite MCP vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services" }, { "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-locationiq.json", "title": "HERE Location Services vs LocationIQ", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json", "title": "HERE Location Services vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.json", "title": "HERE Location Services vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-nextbillion.json", "title": "HERE Location Services vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-nominatim.json", "title": "HERE Location Services vs Nominatim", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json", "title": "HERE Location Services vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json", "title": "HERE Location Services vs Radar", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar" }, { "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-tomtom.json", "title": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" }, { "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-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-woosmap.json", "title": "MapQuest vs Woosmap", "url": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap" }, { "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-woosmap.json", "title": "Nominatim vs Woosmap", "url": "https://www.anchorterminal.com/compare/nominatim-vs-woosmap" }, { "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-woosmap.json", "title": "Radar vs Woosmap", "url": "https://www.anchorterminal.com/compare/radar-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.json", "title": "Stadia Maps vs Woosmap", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap" }, { "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-woosmap.json", "title": "NextBillion.ai vs Woosmap", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-woosmap" } ], "panel": null, "scores": [ { "by": 23, "edge": "woosmap", "here-location-services": 55, "key": "reliability", "name": "Reliability", "weight": 16, "woosmap": 78 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "here-location-services", "here-location-services": 89, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "woosmap": 81 }, { "by": 17, "edge": "here-location-services", "here-location-services": 93, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "woosmap": 76 }, { "by": 22, "edge": "here-location-services", "here-location-services": 65, "key": "security", "name": "Security \u0026 auth", "weight": 14, "woosmap": 43 }, { "by": 30, "edge": "woosmap", "here-location-services": 0, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "woosmap": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 19, "edge": "here-location-services", "here-location-services": 45, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "woosmap": 26 }, { "by": 9, "edge": "here-location-services", "here-location-services": 63, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "woosmap": 54 } ], "summary": "Woosmap scores 59.4 (C) on agent readiness against HERE Location Services's 58.4 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "here-location-services": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. No numeric rate limit or retry guidance was found, prices were unreadable, and HERE's terms bar using its materials with an AI system and bar scraping, so its pages could not be re-read.", "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/here-location-services-vs-woosmap", "json": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.min.md" }, "markdown": "Woosmap scores 59.4 (C) on agent readiness against HERE Location Services's 58.4 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do geocoding.\n\n- HERE Location Services: grade C, 58.4/100, rank #753 of 1510. Markdown https://www.anchorterminal.com/tools/here-location-services.md · JSON https://www.anchorterminal.com/api/v1/tools/here-location-services.json\n- Woosmap: grade C, 59.4/100, rank #707 of 1510. 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### HERE Location Services (C)\n\nGood for: Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.\n\nAhead on:\n- Schema \u0026 documentation, 89 against 81\n- Agent ergonomics, 93 against 76\n- Security \u0026 auth, 65 against 43\n- Maintenance \u0026 community, 45 against 26\n- Transparency \u0026 trust, 63 against 54\n\nWatch for: Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run\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 55\n- Payments \u0026 pricing, 30 against 0\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: No public changelog or release notes for the APIs\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Woosmap +30\n\n- HERE Location Services (0): Readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). No x402, MPP or L402 was found in the docs index or the terms (0). The Base Plan price page is public, but its table is drawn by script and showed no prices to our reader, so per-request prices score as absent, a limit of our reading and not a finding that prices are hidden (0). HERE's docs say a new organisation can get started for free, but whether a card is asked for was not established, so the free-tier line can't be credited (0; the 10 carried isn't a checklist value). Sign-up is a browser flow with email verification (0). Support plans are priced in public, from $50 a month for the Developer plan. 0+0+0+0 = 0.\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### Reliability: Woosmap +23\n\n- HERE Location Services (55): Graded on the REST APIs (Geocoding and Search v7, Routing v8) with the hosted lines. HERE's acceptable use policy bars data mining and scraping of HERE Materials, websites included, so HERE's hosts were not requested on 4 November and the 9 October readings stand. HERE's docs describe a public status page at status.here.com/status with current status, a status history tab and scheduled maintenance (per the 9 October check, not re-read on 4 November) (20). The page was drawn by script on 9 October and is now paused, so the record from 6 August is unread (5). No rate limit with a number was found in the docs; the Base Plan limits sit on a price page drawn by script (0; the 5 carried isn't a checklist value). The Limits and Quotas page says an exceeded quota returns 429 or 503 and that a surge can be throttled for about 10 minutes, and the OpenAPI definition lists 429, with no Retry-After header or backoff guidance and only reads involved (per the 9 October check, not re-read on 4 November). Documented 429 handling without backoff guidance reads at the line's 10 (the 7 carried isn't a checklist value). Monthly availability targets of 99.9 per cent are published for Geocoding and Search v7 and Routing v8, with service credits for the Essential support plan and above (per the 9 October check, not re-read on 4 November) (10). Both APIs are in the Active lifecycle stage (10). 20+5+0+10+10+10 = 55.\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### Security \u0026 auth: HERE Location Services +22\n\n- HERE Location Services (65): All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). Credentials are API keys, OAuth 2.0 client credentials and OAuth 2.1 `private_key_jwt` with a registered JWK, where the private key stays with the customer. Tokens are short-lived and can be scoped to a project, and an app holds two API keys or two JWKs for rotation (30). Less 10 because the documented API key method is the `apiKey` query parameter (20). The location services only read. Trusted domains limit where a key works, and app credentials do not inherit the user's permissions (15 of 20). Results carry place names from third-party sources. The Location Reasoning examples load a `guardrails://location-reasoning-usage-policy` resource and a `hlr___secure_location_reasoning` prompt, whose text was not read (7 of 15). A Usage API reports billable usage by app and project. Per-call logs were not found (6 of 15). ISO/IEC 27001:2022, 27701, 27017, 27018 and 42001 certificates, SOC 2 Type 2 scoped to Platform Foundation and Workspace, TISAX AL3 and CSA STAR Level 2 are listed. A disclosure policy of 13 July 2023 names security@here.com with a 90-day window. No bug bounty and no security.txt were found (17 of 20). Total 65.\n- Woosmap (43): Public keys are read-only and must carry a domain or IP restriction. Private keys are read-only or read and write (fixed at creation), restricted by IP, iOS or Android, and can go in an X-Api-Key header. Less 10 because `private_key` in the query string is a documented option and the default in the spec (17). Read-only keys and the read/write split give least privilege; no confirmation step on dataset deletes was found (16). find_nearby and get_place_details return public POI data, ratings and opening hours, with no prompt-injection guidance (7). Console usage per project wasn't checked (3). www.woosmap.com/.well-known/security.txt returns 404, and we found no disclosure policy, bug bounty or certification (0). 17+16+7+3+0 = 43.\n\n### Maintenance \u0026 community: HERE Location Services +19\n\n- HERE Location Services (45): HERE's changelogs sit on docs.here.com, paused under the acceptable use policy, so entries after 9 October are unread. On the 9 October reading the newest dated entries are Matrix Routing 8.49.0 on 9 September 2026 (a documentation change) and Routing 8.162.0 on 7 September 2026, 58 days before this check (20). From 6 August only Routing 8.161.0 (11 August) and 8.162.0 (7 September) fall in the window, with the Matrix documentation change at half, 2.5 in all and short of three (0, cause time; 8.160.0 of 16 July has left the window). Changelogs are public for each API, and paid support plans state response times from 72 hours down to 4 (10 of 15). HERE's GitHub repositories, read as a third-party host, show the HERE SDK for Android, iOS and Flutter current, with example apps tagged for releases 4.27.2.0 (17 August), 4.27.3.0 (3 September), 4.28.0.0 (1 October) and 4.28.1.0 (2 November 2026), and their search and routing engines are the SDKs the ergonomics note credits. The Python client for the REST APIs has carried a deprecation notice since 5 September 2023. These SDK releases aren't counted on the release lines, because their release notes sit on HERE's paused pages and nothing read shows them changing the location services (15; the 5 carried isn't a checklist value). Package health isn't visible for a closed service, and the SDK examples repository has no CI workflow (0; the 5 carried isn't a checklist value). 20+0+10+15+0 = 45.\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### Agent ergonomics: HERE Location Services +17\n\n- HERE Location Services (93): All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). `limit` sizes geocoding responses (1 to 100, default 20), and `show` and `return` parameters add optional blocks only when asked for. The MCP server lists 13 tools, two of them experimental, and passes cached route and isoline IDs between tools so geometry is not returned twice (18 of 25). Filters by country, result type, position and bounding area and a result limit are documented, with no offset or cursor paging for geocoding (20; the 15 carried isn't a checklist value, and filters with a size limit meet the line). Errors carry `status`, `title`, `code`, `cause`, `action` and `correlationId`, and the routing changelog names error codes such as `E605502` (20; the 17 carried isn't a checklist value). The location calls are reads and safe to repeat (20; the 14 carried isn't a checklist value; MCP annotations were not read). A geocode needs only `q` and a credential, and HERE publishes SDKs in JavaScript, Android, iOS and Flutter, for maps rather than as REST clients (15; the 10 carried isn't a checklist value). 18+20+20+20+15 = 93.\n- Woosmap (76): API reading, with the hosted MCP server's nine tools as a second surface. Localities and Stores responses can be narrowed by type, components and fields, and the MCP set is small (20). Store search takes query filters, radius and paging, and the Distance Matrix has an async mode for large jobs (17). Documented error codes including 402 for billing and 429 with reset timing (17). Reads are safe to retry, but no idempotency key was found for the Datasets and Stores write endpoints, and the MCP docs don't mention tool annotations (10). Official JavaScript, iOS and Android SDKs and samples in Python and JavaScript, with few required parameters (12). 20+17+17+10+12 = 76.\n\n### Transparency \u0026 trust: HERE Location Services +9\n\n- HERE Location Services (63): All readings per the 9 October check, not re-read on 4 November (HERE's hosts paused). Closed service under public, dated terms. The HERE Platform Terms, effective 18 September 2023, name the contracting entity by region and govern the Base Plan (15 of 30). The terms say HERE analyses use of the platform and uses anonymised or aggregated findings to develop its products, and Essential Data Processing domains switch that off. The privacy policy of 29 August 2024 says it does not cover processing done on behalf of customers and gives no retention periods. The DPA is a PDF we did not read (14 of 30). The Product Lifecycle Policy gives six months' notice before discontinuation and 6 to 12 months for a deprecated feature, and changelogs mark deprecations with dates (20). No sub-processor list or data location was found on the pages read (3 of 20). Total 52.\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## Score by category\n\n| Category | Weight | HERE Location Services | Woosmap | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 78 | Woosmap +23 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 89 | 81 | HERE Location Services +8 |\n| Agent ergonomics | 13% (16.2 this run) | 93 | 76 | HERE Location Services +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 43 | HERE Location Services +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 30 | Woosmap +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 45 | 26 | HERE Location Services +19 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 54 | HERE Location Services +9 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58.4 · C** | **59.4 · C** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | Woosmap |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | WOOSMAP SAS |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://api.woosmap.com/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | none |\n| Tools exposed | 13 | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-09-09 | none |\n| Terms last updated | 2023-09-18 | no date given |\n| Privacy policy last updated | 2024-08-29 | 2024-07-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## How the scores have moved\n\n### HERE Location Services\n\n- +0.4 on 4 November 2026: correction, time\n\n### Woosmap\n\nNo score change since it was listed.\n\n## Verdicts\n\n**HERE Location Services.** Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. No numeric rate limit or retry guidance was found, prices were unreadable, and HERE's terms bar using its materials with an AI system and bar scraping, so its pages could not be re-read.\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### HERE Location Services\n\n1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL\n2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response\n3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota\n4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support\n5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`\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, HERE Location Services or Woosmap?\n\nWoosmap scores 59.4 (C) on agent readiness against HERE Location Services's 58.4 (C), and leads in 2 of 7 scored categories. HERE Location Services leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do HERE Location Services and Woosmap need an API key?\n\nHERE Location Services takes an API key or an OAuth sign-in. Woosmap needs an API key.\n\n### Can an agent call HERE Location Services and Woosmap without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Woosmap at https://api.woosmap.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"woosmap\"}`. From a terminal: `anchor compare here-location-services woosmap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json\n\n## Other comparisons with HERE Location Services or Woosmap\n\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)\n- [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md)\n- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)\n- [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)\n- [Geocodio vs HERE Location Services](https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)\n- [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.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 LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs MapTiler Cloud](https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.md)\n- [HERE Location Services vs NextBillion.ai](https://www.anchorterminal.com/compare/here-location-services-vs-nextbillion.md)\n- [HERE Location Services vs Nominatim](https://www.anchorterminal.com/compare/here-location-services-vs-nominatim.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.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 TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md)\n- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md)\n- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md)\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)\n- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)\n- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-vs-woosmap.md)\n- [Radar vs Woosmap](https://www.anchorterminal.com/compare/radar-vs-woosmap.md)\n- [Stadia Maps vs Woosmap](https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md)\n- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.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": "HERE Location Services vs Woosmap", "url": "" } ], "description": "Woosmap scores 59.4 (C) to HERE Location Services's 58.4 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HERE Location Services C 58.4", "Woosmap C 59.4", "scores" ], "h1": "HERE Location Services vs Woosmap", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/here-location-services-vs-woosmap", "published": "2026-10-01", "section": "tools", "title": "HERE Location Services vs Woosmap for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap" }, "tokens": { "markdown": 5700, "slim": 3430 }, "version": 1 }