{ "data": { "a": { "slug": "locationiq", "name": "LocationIQ", "vendor": "LocationIQ (Unwired Labs)", "vendorUrl": "https://locationiq.com", "kind": "http-api", "category": "maps", "summary": "Forward and reverse geocoding, autocomplete, nearby places, directions, matrix and map tiles, from US and EU endpoints.", "url": "https://www.anchorterminal.com/tools/locationiq", "markdownUrl": "https://www.anchorterminal.com/tools/locationiq.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/locationiq.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/locationiq.json", "dns": "locationiq.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://us1.locationiq.com/v1", "packages": [], "auth": "api-key", "authNotes": "Access token passed as the key query parameter. Same API on us1.locationiq.com and eu1.locationiq.com.", "pricing": "freemium", "pricingNotes": "Free 5,000 requests a day at 2 a second, no card, with a prominent link back required. Maps Lite $45 a month (10,000 a day, maps only), Developer $100 (25,000 a day, all APIs), Startup $200 (60,000 a day), Growth Plus $500 (7.5 million a month), Business Plus $950 (30 million a month), Enterprise custom. Paid plans need a card (https://locationiq.com/pricing).", "priceSummary": "$100 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.locationiq.com", "llmsTxt": "https://docs.locationiq.com/llms.txt", "openapi": "https://docs.locationiq.com/openapi.yaml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "llms-txt", "free-tier", "no-card", "eu", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 655, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 3, "payments": 30, "reliability": 83, "schema": 78, "security": 55, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.", "bestFor": "A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.", "strengths": [ "5,000 free requests a day with no card, commercial use allowed with a link back", "Public OpenAPI 3.0 spec and an llms.txt with Markdown pages", "Scoped tokens with referrer or IP restrictions and per-token rate limits", "No incidents posted between 2 April and 1 October 2026 on the status page, with history back to 2018", "Error messages that separate per-second, per-minute and per-day limits" ], "weaknesses": [ "No changelog, release notes or blog", "Official SDKs untouched since 2020", "No MCP server", "Key only in the query string", "Free plan must delete cached results after 48 hours and gets a single token" ], "agentNotes": [ "Use eu1.locationiq.com for European users or data", "Add format=json and limit=1 to keep responses small", "On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day", "Call /balance before a large batch to see what's left of the day's quota", "Redact the key parameter before logging request URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 74, "maintenance": 3, "payments": 30, "reliability": 83, "schema": 78, "security": 55, "transparency": 40 }, "provenanceScore": 82, "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-10-08", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://eu1.locationiq.com/v1/search?key=$LOCATIONIQ_API_KEY\u0026q=10%20Downing%20Street%2C%20London\u0026format=json\u0026limit=1\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/locationiq" }, "area": "everyday", "unitPrices": [ { "item": "Developer plan", "unit": "month", "usd": 100, "note": "25,000 requests a day, 20 a second, all APIs" }, { "item": "Startup plan", "unit": "month", "usd": 200, "note": "60,000 requests a day, 22 a second" }, { "item": "Growth Plus plan", "unit": "month", "usd": 500, "note": "7.5 million requests a month, 30 a second" }, { "item": "Business Plus plan", "unit": "month", "usd": 950, "note": "30 million requests a month, 40 a second" } ], "provenance": { "legalEntity": "Unwired Labs (India) Pvt Ltd", "domain": "locationiq.com", "domainRegistered": "2005-09-20", "endpointOnVendorDomain": true, "terms": "https://locationiq.com/tos", "privacy": "https://locationiq.com/privacy", "statusPage": "https://status.locationiq.com", "changelog": "", "securityTxt": "valid", "checked": "2026-11-04", "notes": [ "The terms were last updated 31 March 2026 (re-read on 4 November).", "security.txt lists hello@locationiq.com and expires 2028-01-01 (re-read on 4 November).", "LocationIQ's own privacy policy is at locationiq.com/privacy, last updated 22 May 2020. The parent's page at unwiredlabs.com/privacy embeds a Google Doc our reader couldn't see.", "The status page's RSS feed held 74 incidents from March 2018 to 2 April 2026 on 1 October. On 4 November status.locationiq.com answered robots.txt with its app page, so it wasn't read.", "We found no changelog or blog." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/locationiq.json", "live": { "slug": "locationiq", "probe": { "target": "https://us1.locationiq.com/v1", "method": "get", "lastAt": "2026-11-07T18:20:35.848411072Z", "lastOk": true, "lastStatus": 403, "lastMs": 309, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 238, "p95ms24h": 430, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 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": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.locationiq.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:00.589936264Z" }, "securityTxt": { "url": "https://locationiq.com/.well-known/security.txt", "state": "valid", "expires": "2028-01-01T00:00:00Z", "checkedAt": "2026-11-07T16:01:08.426296864Z" }, "llmsTxt": { "url": "https://docs.locationiq.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:54.459912203Z" }, "domain": { "domain": "locationiq.com", "registered": "2005-09-20", "source": "https://rdap.verisign.com/com/v1/domain/locationiq.com", "checkedAt": "2026-11-01T14:12:18.326873505Z" }, "pages": [ { "url": "https://locationiq.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:13:26.63045639Z", "changedAt": "2026-10-24T02:20:44.840309825Z", "fingerprint": "aaab3bd9280a" }, { "url": "https://locationiq.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:28.786968548Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f99922f73f1e" }, { "url": "https://locationiq.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:30.695378865Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "13f087788a40" } ], "updatedAt": "2026-11-07T18:20:35.848411072Z" } }, "answer": "LocationIQ and Woosmap score within a point of each other on agent readiness, 60.3 (C) and 59.4 (C). Woosmap leads on maintenance \u0026 community.", "b": { "slug": "woosmap", "name": "Woosmap", "vendor": "WOOSMAP SAS", "vendorUrl": "https://www.woosmap.com", "kind": "http-api", "category": "maps", "summary": "Woosmap is a French location platform with REST APIs for address autocomplete and geocoding (Localities), store search, distance and routing, geolocation, indoor maps and map display, plus a hosted MCP server for AI assistants.", "url": "https://www.anchorterminal.com/tools/woosmap", "markdownUrl": "https://www.anchorterminal.com/tools/woosmap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/woosmap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/woosmap.json", "dns": "woosmap.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.woosmap.com/mcp", "packages": [], "auth": "api-key", "authNotes": "Keys from the Woosmap Console after a browser signup. Public keys (woos-...) are read-only and must be restricted to domains or IPs. Private keys are read-only or read and write, fixed at creation, restricted by IP, iOS or Android, and sent as the X-Api-Key header or the private_key query parameter. The MCP server takes a private key in the X-Api-Key header.", "pricing": "freemium", "pricingNotes": "Free plan up to 10,000 API requests a month with no credit card. Pro uses public volume tiers per API, shown in a calculator, and can be bought through AWS Marketplace. Enterprise is by quote with volume discounts, data caching options and a 99.9% SLA.", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, llms.txt or pricing page (checked 2026-11-06). The spec documents a 402 response for billing, not a payment protocol.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developers.woosmap.com/", "llmsTxt": "https://developers.woosmap.com/llms.txt", "openapi": "https://developers.woosmap.com/assets/woosmap-openapi3.json", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "status-page", "enterprise", "sla", "eu", "android", "ios", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 59.4, "grade": "C", "agentReady": false, "rank": 704, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 26, "payments": 30, "reliability": 78, "schema": 81, "security": 43, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Woosmap publishes an OpenAPI 3.1 spec, llms.txt with Markdown pages, per-endpoint rate limits and 429 retry rules, plus a hosted nine-tool MCP server. No changelog, security.txt, API data retention statement or readable per-request price was found, and private keys can travel in the query string.", "bestFor": "Store locators, address autocomplete and distance for retail and logistics teams that keep their own location data in the platform, with an MCP server for agents.", "strengths": [ "OpenAPI 3.1 spec with 47 paths, llms.txt routing index and Markdown twins of every page", "Per-endpoint rate limits with RateLimit headers and explicit 429 retry rules and sample code", "Hosted MCP server at api.woosmap.com/mcp with nine tools, including search over the customer's own store data", "Read-only and read/write private keys with IP, iOS or Android restrictions and an X-Api-Key header", "Free plan of 10,000 requests a month with no card" ], "weaknesses": [ "No public changelog or release notes for the APIs", "No security.txt, disclosure policy or certification found", "The privacy policy covers the website only, with nothing on API data retention", "Per-request prices aren't readable without the script-driven calculator", "`private_key` in the query string is documented and is the spec's default scheme" ], "agentNotes": [ "Send the private key in the X-Api-Key header, not the private_key query parameter", "Use a read-only private key for the MCP server unless the task writes stores or datasets", "On 429 wait the `t` seconds from the RateLimit header, retry at most three times, and pause batches when `r` reaches 0", "Use find_stores_nearby for the customer's own locations and find_nearby for public POIs", "Read endpoint parameters from the /api-reference/ Markdown pages, which llms.txt marks as authoritative" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.4 } ], "editorialScores": { "ergonomics": 76, "maintenance": 26, "payments": 30, "reliability": 78, "schema": 81, "security": 43, "transparency": 31 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"X-Api-Key: $WOOSMAP_PRIVATE_KEY\" \"https://api.woosmap.com/localities/geocode?address=Place+de+la+Comedie+Montpellier\"", "config": { "mcpServers": { "woosmap": { "args": [ "mcp-remote", "https://api.woosmap.com/mcp", "--header", "X-Api-Key: PRIVATE_KEY" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/woosmap" }, "area": "everyday", "provenance": { "legalEntity": "WOOSMAP SAS", "domain": "woosmap.com", "domainRegistered": "2010-06-04", "endpointOnVendorDomain": true, "terms": "https://www.woosmap.com/policies/terms-online", "privacy": "https://www.woosmap.com/policies/privacy", "statusPage": "https://status.woosmap.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The online terms name WOOSMAP, a French SAS at 5 rue du Plan du Palais, 34000 Montpellier, RCS Montpellier 983 770 405, represented by its CEO Jean-Thomas Rouzin. The legal notice (effective 1 July 2024) gives SAS capital of €10,821,200 and AWS as the site host.", "status.woosmap.com's robots.txt disallows /api/ and /embed/. A request to /api/v2/incidents.json was sent by mistake on 6 November 2026 before robots.txt was read; its contents are not used anywhere in this listing.", "www.woosmap.com/.well-known/security.txt returns 404.", "No public API changelog was found. developers.woosmap.com/changelog/ and /release-notes/ return 404.", "RDAP gives woosmap.com a registration date of 4 June 2010. robots.txt on www.woosmap.com and developers.woosmap.com allows these pages, and the developer site's robots.txt allows llms.txt by name." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/woosmap.json", "live": { "slug": "woosmap", "probe": { "target": "https://api.woosmap.com/mcp", "method": "get", "lastAt": "2026-11-07T18:21:05.894098339Z", "lastOk": true, "lastStatus": 401, "lastMs": 219, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 48, "p95ms24h": 118, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.woosmap.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:22:11.709282208Z" }, "securityTxt": { "url": "https://woosmap.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:21.81706489Z" }, "llmsTxt": { "url": "https://developers.woosmap.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:23.501072242Z" }, "pages": [ { "url": "https://www.woosmap.com/policies/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:37:14.116262014Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99523833ae5e" }, { "url": "https://www.woosmap.com/policies/terms-online", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:19.402817389Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6252e1bc3d91" } ], "updatedAt": "2026-11-07T18:22:11.709282208Z" } }, "edges": [ { "by": 23, "category": "maintenance", "leads": "woosmap", "name": "Maintenance \u0026 community", "reasons": { "a": "We found no changelog, release notes or blog on 4 November (docs.locationiq.com/changelog, locationiq.com/changelog and locationiq.com/blog all return 404, and llms.txt lists none), so there's no dated API change to count. The terms were updated 31 March 2026, which isn't an API change (0). No dated entries in the last 90 days (0). No public changelog. Support is by email, which we didn't test (3). The official Python client hasn't changed since 30 March 2020 (0). Nothing current to judge package health by (0). The status page shows the service is run and watched, which this checklist doesn't capture. 0+0+3+0+0 = 3.", "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": 3, "b": 26 } }, { "by": 12, "category": "security", "leads": "locationiq", "name": "Security \u0026 auth", "reasons": { "a": "Separate tokens per application, each with scopes, HTTP referrer or IP restrictions (up to 5 CIDRs), its own rate limits, and rotation from the dashboard, which earns 30. Less 10 because the OpenAPI spec defines only the key query parameter. The free plan gets one token (20). Scopes and per-token limits give least privilege, and nothing writes (17). Results are OpenStreetMap-derived text with no prompt-injection guidance (7). The /balance endpoint shows remaining quota. We didn't check per-call logs (4). security.txt valid to 1 January 2028, re-read on 4 November, pointing to hello@locationiq.com. No bug bounty or certification found (7).", "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": 55, "b": 43 } }, { "by": 7, "category": "transparency", "leads": "locationiq", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with readable terms, updated 31 March 2026, under the laws of Telangana, India (15). The terms are specific on storage, 48 hours on Free and for as long as you're a customer on paid plans, with no server-side tile caching. The privacy policy at locationiq.com/privacy was last updated 22 May 2020, says IP addresses are stored to check for abuse with no retention period, and links a DPA (15). No deprecation policy or notices found (0). Stripe, Zoho and Google Analytics named without locations. Data centre regions are visible on the status page, not in the policy (10).", "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": 61, "b": 54 } }, { "by": 5, "category": "reliability", "leads": "locationiq", "name": "Reliability", "reasons": { "a": "status.locationiq.com lists 15 components by data centre (geocoding, autocomplete, maps and routing in Europe, US East, US West and Asia Pacific) with RSS and Atom history back to March 2018, 74 incidents in all, per the 1 October check (20). The newest incident then was 'Network Issues' on 2 April 2026, so 6 August to 1 October was clean. On 4 November the status host answered robots.txt with its app page, so nothing more was requested there, 2 October to 4 November is unread, and the line is held at what the read part supports (30). Per-second and daily limits for every plan, and per-token and per-IP limits on top, with soft daily limits of up to 100% more on paid plans (15). Three distinct 429 messages, Rate Limited Second, Minute and Day, and a 500 that says to retry after a short wait, but no Retry-After or backoff guidance (8). No SLA. The pricing page lists custom SLAs only on its top plan and points to public uptime instead (0). GA (10). 20+30+15+8+0+10 = 83.", "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": 83, "b": 78 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "LocationIQ (Unwired Labs)", "b": "WOOSMAP SAS", "name": "Vendor" }, { "a": "https://us1.locationiq.com/v1", "b": "https://api.woosmap.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-03-31", "b": "no date given", "name": "Terms last updated" }, { "a": "2020-05-22", "b": "2024-07-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "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" }, { "a": "4.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "LocationIQ and Woosmap score within a point of each other on agent readiness, 60.3 (C) and 59.4 (C). Woosmap leads on maintenance \u0026 community.", "question": "Which is better for AI agents, LocationIQ or Woosmap?" }, { "answer": "Both need an API key.", "question": "Do LocationIQ and Woosmap need an API key?" }, { "answer": "Yes. LocationIQ has a hosted endpoint at https://us1.locationiq.com/v1 and Woosmap at https://api.woosmap.com/mcp.", "question": "Can an agent call LocationIQ and Woosmap without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 83 against 78", "Security \u0026 auth, 55 against 43", "Transparency \u0026 trust, 61 against 54" ], "also": null, "goodFor": "A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.", "slug": "locationiq", "watchFor": "No changelog, release notes or blog" }, { "aheadOn": [ "Maintenance \u0026 community, 26 against 3" ], "also": null, "goodFor": "Store locators, address autocomplete and distance for retail and logistics teams that keep their own location data in the platform, with an MCP server for agents.", "slug": "woosmap", "watchFor": "No public changelog or release notes for the APIs" } ], "history": { "locationiq": [ { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 60.6, "fromGrade": "C", "to": 60.3, "toGrade": "C" } ], "woosmap": null }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.json", "title": "Amazon Location Service vs LocationIQ", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-locationiq" }, { "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-locationiq.json", "title": "ArcGIS Location Platform vs LocationIQ", "url": "https://www.anchorterminal.com/compare/arcgis-vs-locationiq" }, { "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-locationiq.json", "title": "Azure Maps vs LocationIQ", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-locationiq" }, { "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-locationiq.json", "title": "Geoapify Location Platform + MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geoapify-vs-locationiq" }, { "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-locationiq.json", "title": "Geocodio vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geocodio-vs-locationiq" }, { "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-locationiq.json", "title": "Google Maps Platform + Grounding Lite MCP vs LocationIQ", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-locationiq" }, { "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-woosmap.json", "title": "HERE Location Services vs Woosmap", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox.json", "title": "LocationIQ vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest.json", "title": "LocationIQ vs MapQuest", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler.json", "title": "LocationIQ vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-nextbillion.json", "title": "LocationIQ vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/locationiq-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim.json", "title": "LocationIQ vs Nominatim", "url": "https://www.anchorterminal.com/compare/locationiq-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-opencage.json", "title": "LocationIQ vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/locationiq-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-radar.json", "title": "LocationIQ vs Radar", "url": "https://www.anchorterminal.com/compare/locationiq-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.json", "title": "LocationIQ vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom.json", "title": "LocationIQ vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/locationiq-vs-tomtom" }, { "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": 5, "edge": "locationiq", "key": "reliability", "locationiq": 83, "name": "Reliability", "weight": 16, "woosmap": 78 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "woosmap", "key": "schema", "locationiq": 78, "name": "Schema \u0026 documentation", "weight": 13, "woosmap": 81 }, { "by": 2, "edge": "woosmap", "key": "ergonomics", "locationiq": 74, "name": "Agent ergonomics", "weight": 13, "woosmap": 76 }, { "by": 12, "edge": "locationiq", "key": "security", "locationiq": 55, "name": "Security \u0026 auth", "weight": 14, "woosmap": 43 }, { "by": 0, "edge": "", "key": "payments", "locationiq": 30, "name": "Payments \u0026 pricing", "weight": 10, "woosmap": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 23, "edge": "woosmap", "key": "maintenance", "locationiq": 3, "name": "Maintenance \u0026 community", "weight": 7, "woosmap": 26 }, { "by": 7, "edge": "locationiq", "key": "transparency", "locationiq": 61, "name": "Transparency \u0026 trust", "weight": 7, "woosmap": 54 } ], "summary": "LocationIQ and Woosmap score within a point of each other on agent readiness, 60.3 (C) and 59.4 (C). Woosmap leads on maintenance \u0026 community. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "locationiq": "5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.", "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/locationiq-vs-woosmap", "json": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap.min.md" }, "markdown": "LocationIQ and Woosmap score within a point of each other on agent readiness, 60.3 (C) and 59.4 (C). Woosmap leads on maintenance \u0026 community. Both do geocoding.\n\n- LocationIQ: grade C, 60.3/100, rank #655 of 1486. Markdown https://www.anchorterminal.com/tools/locationiq.md · JSON https://www.anchorterminal.com/api/v1/tools/locationiq.json\n- Woosmap: grade C, 59.4/100, rank #704 of 1486. Markdown https://www.anchorterminal.com/tools/woosmap.md · JSON https://www.anchorterminal.com/api/v1/tools/woosmap.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### LocationIQ (C)\n\nGood for: A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.\n\nAhead on:\n- Reliability, 83 against 78\n- Security \u0026 auth, 55 against 43\n- Transparency \u0026 trust, 61 against 54\n\nWatch for: No changelog, release notes or blog\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- Maintenance \u0026 community, 26 against 3\n\nWatch for: No public changelog or release notes for the APIs\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Woosmap +23\n\n- LocationIQ (3): We found no changelog, release notes or blog on 4 November (docs.locationiq.com/changelog, locationiq.com/changelog and locationiq.com/blog all return 404, and llms.txt lists none), so there's no dated API change to count. The terms were updated 31 March 2026, which isn't an API change (0). No dated entries in the last 90 days (0). No public changelog. Support is by email, which we didn't test (3). The official Python client hasn't changed since 30 March 2020 (0). Nothing current to judge package health by (0). The status page shows the service is run and watched, which this checklist doesn't capture. 0+0+3+0+0 = 3.\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### Security \u0026 auth: LocationIQ +12\n\n- LocationIQ (55): Separate tokens per application, each with scopes, HTTP referrer or IP restrictions (up to 5 CIDRs), its own rate limits, and rotation from the dashboard, which earns 30. Less 10 because the OpenAPI spec defines only the key query parameter. The free plan gets one token (20). Scopes and per-token limits give least privilege, and nothing writes (17). Results are OpenStreetMap-derived text with no prompt-injection guidance (7). The /balance endpoint shows remaining quota. We didn't check per-call logs (4). security.txt valid to 1 January 2028, re-read on 4 November, pointing to hello@locationiq.com. No bug bounty or certification found (7).\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### Transparency \u0026 trust: LocationIQ +7\n\n- LocationIQ (61): Closed service with readable terms, updated 31 March 2026, under the laws of Telangana, India (15). The terms are specific on storage, 48 hours on Free and for as long as you're a customer on paid plans, with no server-side tile caching. The privacy policy at locationiq.com/privacy was last updated 22 May 2020, says IP addresses are stored to check for abuse with no retention period, and links a DPA (15). No deprecation policy or notices found (0). Stripe, Zoho and Google Analytics named without locations. Data centre regions are visible on the status page, not in the policy (10).\n- Woosmap (54): Editorial half only. Closed service under online terms that name WOOSMAP SAS of Montpellier and the Commercial Court of Paris (15). The privacy policy covers website visitors only, and we found no statement on how long API request data is kept (5). The pricing page says the Address API is 'being deprecated for Pro Plan subscriptions', with no date (5). The legal notice says the site is hosted by Amazon Web Services; no sub-processor list or data location for the APIs was found (6). 15+5+5+6 = 31.\n\n### Reliability: LocationIQ +5\n\n- LocationIQ (83): status.locationiq.com lists 15 components by data centre (geocoding, autocomplete, maps and routing in Europe, US East, US West and Asia Pacific) with RSS and Atom history back to March 2018, 74 incidents in all, per the 1 October check (20). The newest incident then was 'Network Issues' on 2 April 2026, so 6 August to 1 October was clean. On 4 November the status host answered robots.txt with its app page, so nothing more was requested there, 2 October to 4 November is unread, and the line is held at what the read part supports (30). Per-second and daily limits for every plan, and per-token and per-IP limits on top, with soft daily limits of up to 100% more on paid plans (15). Three distinct 429 messages, Rate Limited Second, Minute and Day, and a 500 that says to retry after a short wait, but no Retry-After or backoff guidance (8). No SLA. The pricing page lists custom SLAs only on its top plan and points to public uptime instead (0). GA (10). 20+30+15+8+0+10 = 83.\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## Score by category\n\n| Category | Weight | LocationIQ | Woosmap | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 83 | 78 | LocationIQ +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 81 | Woosmap +3 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 76 | Woosmap +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 55 | 43 | LocationIQ +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 3 | 26 | Woosmap +23 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 54 | LocationIQ +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **59.4 · C** | |\n\n## Facts side by side\n\n| Fact | LocationIQ | Woosmap |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | LocationIQ (Unwired Labs) | WOOSMAP SAS |\n| Hosted endpoint | `https://us1.locationiq.com/v1` | `https://api.woosmap.com/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Terms last updated | 2026-03-31 | no date given |\n| Privacy policy last updated | 2020-05-22 | 2024-07-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | 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| Agent reviews | 4.5/5 (2) | none |\n\n## How the scores have moved\n\n### LocationIQ\n\n- -0.3 on 8 October 2026: checklist\n\n### Woosmap\n\nNo score change since it was listed.\n\n## Verdicts\n\n**LocationIQ.** 5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.\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### LocationIQ\n\n1. Use eu1.locationiq.com for European users or data\n2. Add format=json and limit=1 to keep responses small\n3. On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day\n4. Call /balance before a large batch to see what's left of the day's quota\n5. Redact the key parameter before logging request URLs\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, LocationIQ or Woosmap?\n\nLocationIQ and Woosmap score within a point of each other on agent readiness, 60.3 (C) and 59.4 (C). Woosmap leads on maintenance \u0026 community.\n\n### Do LocationIQ and Woosmap need an API key?\n\nBoth need an API key.\n\n### Can an agent call LocationIQ and Woosmap without installing anything?\n\nYes. LocationIQ has a hosted endpoint at https://us1.locationiq.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/locationiq-vs-woosmap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/locationiq-vs-woosmap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"locationiq\", \"b\": \"woosmap\"}`. From a terminal: `anchor compare locationiq woosmap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/locationiq.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json\n\n## Other comparisons with LocationIQ or Woosmap\n\n- [Amazon Location Service vs LocationIQ](https://www.anchorterminal.com/compare/amazon-location-vs-locationiq.md)\n- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)\n- [ArcGIS Location Platform vs LocationIQ](https://www.anchorterminal.com/compare/arcgis-vs-locationiq.md)\n- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)\n- [Azure Maps vs LocationIQ](https://www.anchorterminal.com/compare/azure-maps-vs-locationiq.md)\n- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)\n- [Geoapify Location Platform + MCP vs LocationIQ](https://www.anchorterminal.com/compare/geoapify-vs-locationiq.md)\n- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)\n- [Geocodio vs LocationIQ](https://www.anchorterminal.com/compare/geocodio-vs-locationiq.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)\n- [Google Maps Platform + Grounding Lite MCP vs LocationIQ](https://www.anchorterminal.com/compare/google-maps-platform-vs-locationiq.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 Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md)\n- [LocationIQ vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-mapbox.md)\n- [LocationIQ vs MapQuest](https://www.anchorterminal.com/compare/locationiq-vs-mapquest.md)\n- [LocationIQ vs MapTiler Cloud](https://www.anchorterminal.com/compare/locationiq-vs-maptiler.md)\n- [LocationIQ vs NextBillion.ai](https://www.anchorterminal.com/compare/locationiq-vs-nextbillion.md)\n- [LocationIQ vs Nominatim](https://www.anchorterminal.com/compare/locationiq-vs-nominatim.md)\n- [LocationIQ vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/locationiq-vs-opencage.md)\n- [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.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": "LocationIQ vs Woosmap", "url": "" } ], "description": "LocationIQ and Woosmap score within a point of each other for geocoding, 60.3 and 59.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "LocationIQ C 60.3", "Woosmap C 59.4", "scores" ], "h1": "LocationIQ vs Woosmap", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/locationiq-vs-woosmap", "published": "2026-10-01", "section": "tools", "title": "LocationIQ vs Woosmap for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/locationiq-vs-woosmap" }, "tokens": { "markdown": 3900, "slim": 2030 }, "version": 1 }