{ "data": { "a": { "slug": "mapquest", "name": "MapQuest", "vendor": "MapQuest (System1)", "vendorUrl": "https://developer.mapquest.com", "kind": "http-api", "category": "maps", "summary": "MapQuest's location APIs cover geocoding, directions, route matrices, place search, traffic and static maps. Agents call the REST API with a key or connect to a hosted MCP server over OAuth.", "url": "https://www.anchorterminal.com/tools/mapquest", "markdownUrl": "https://www.anchorterminal.com/tools/mapquest.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mapquest.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mapquest.json", "dns": "mapquest.grade.anchorterminal.com", "license": "Proprietary service. No API terms were found published without a login", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://www.mapquestapi.com", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A person registers at developer.mapquest.com and creates an API key. REST calls send it in the `key` query parameter. The MCP server uses OAuth through login.mapquest.com with the single scope `mcp:tools`, then picks one of the account's keys. Further keys can be created with `POST /account/v1/keys`.", "pricing": "usage", "pricingNotes": "MapQuestGO is pay-as-you-go at $0.0045 a transaction with no monthly minimum, after 50,000 one-time free transactions that expire on 1 January 2027. Monthly plans run from Basic at $119 (30,000 transactions) to Business Plus at $949 (500,000). Enterprise is by quote. An agent can start on the free credits without a contract. Whether sign-up needs a card was not established (https://developer.mapquest.com/plans, checked 2026-10-08).", "priceSummary": "$4.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the plans page, llms.txt or the MCP endpoint's 401 response (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.mapquest.com/documentation/", "llmsTxt": "https://developer.mapquest.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.routing", "geo.places" ], "tags": [ "hosted", "mcp", "oauth", "api-key", "llms-txt", "free-credits", "usage-priced", "closed-source" ], "lastRelease": "2026-07-16", "graded": true, "anchor": { "graded": true, "score": 35.4, "grade": "F", "agentReady": false, "rank": 1373, "ranked": true, "rankOf": 1486, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 31 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.", "bestFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "strengths": [ "Hosted MCP server at `https://www.mapquestapi.com/mcp` with OAuth and published protected-resource metadata", "Pay-as-you-go price of $0.0045 a transaction published without a login, with 50,000 one-time free transactions", "The Account API creates and lists keys and reports usage by key, service and hour", "`llms.txt` indexes every REST API, SDK and tool with a one-line purpose", "Async batch geocoding accepts up to 1 million rows, and batch calls take 100 locations" ], "weaknesses": [ "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only", "No status page, changelog or published rate-limit numbers found", "REST keys are sent in the `key` query parameter, and no key scopes or restrictions are documented", "`openapi.json` describes the marketing site and has no paths, so the product APIs have no machine-readable contract", "Monthly plans forbid storing or caching geocodes. That needs an Enterprise account" ], "agentNotes": [ "Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use", "Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs", "Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body", "Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small", "Do not store or cache geocodes on a monthly or pay-as-you-go plan" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 35.4 } ], "editorialScores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 21 }, "provenanceScore": 41, "checked": { "categories": { "ergonomics": "2026-10-08", "maintenance": "2026-10-08", "payments": "2026-10-08", "reliability": "2026-10-08", "schema": "2026-10-08", "security": "2026-10-08", "transparency": "2026-10-08" }, "last": "2026-10-08", "lastMoved": "2026-10-28", "oldest": "2026-10-08", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://www.mapquestapi.com/geocoding/v1/address?key=$MAPQUEST_API_KEY\u0026location=Washington,DC\u0026maxResults=1\u0026thumbMaps=false\"", "claudeCode": "claude mcp add --transport http mapquest https://www.mapquestapi.com/mcp", "config": { "mcpServers": { "mapquest": { "url": "https://www.mapquestapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/mapquest" }, "area": "everyday", "unitPrices": [ { "item": "MapQuestGO pay-as-you-go", "unit": "1k-requests", "usd": 4.5, "note": "$0.0045 a transaction after 50,000 one-time free transactions" }, { "item": "Basic plan", "unit": "month", "usd": 119, "note": "30,000 transactions a month" }, { "item": "Plus plan", "unit": "month", "usd": 249, "note": "75,000 transactions a month" }, { "item": "Business plan", "unit": "month", "usd": 499, "note": "200,000 transactions a month" }, { "item": "Business Plus plan", "unit": "month", "usd": 949, "note": "500,000 transactions a month" } ], "provenance": { "legalEntity": "Mapquest Holdings LLC", "domain": "mapquest.com", "domainRegistered": "1996-01-10", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The developer site's footer reads '© 2026 Mapquest Holdings LLC, A System1 Company'.", "No terms link is given. The site's Terms of Use link, and developer.mapquest.com/legal, lead to https://system1.com/terms/terms-of-use, the parent's website terms (last updated 26 February 2021), which allow personal, non-commercial use only and do not mention the APIs. We found no API or platform terms published without a login.", "No privacy link is given. The only privacy document linked is the System1 OpCo, LLC group privacy policy at https://system1.com/terms/privacy-policy (last updated 5 July 2023), a parent company's notice.", "The REST API and the MCP server answer at www.mapquestapi.com, a second domain (registered 2008-09-08 per RDAP). MapQuest's own docs name that host. OAuth runs at login.mapquest.com.", "developer.mapquest.com/.well-known/security.txt redirects to the home page, www.mapquestapi.com/.well-known/security.txt returns 404, and www.mapquest.com returned an empty 202 to our reader.", "No status page is linked from the developer site, the docs or the plans page. No changelog was found. The blog carries two product announcements dated 16 July 2026.", "RDAP for mapquest.com gives a registration date of 1996-01-10." ], "score": 41 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mapquest.json", "live": { "slug": "mapquest", "probe": { "target": "https://www.mapquestapi.com", "method": "get", "lastAt": "2026-11-07T18:20:37.631736415Z", "lastOk": true, "lastStatus": 404, "lastMs": 325, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 274, "p95ms24h": 357, "samples24h": 239, "samples30d": 7420, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "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 } ] }, "securityTxt": { "url": "https://mapquest.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:01:46.794353638Z" }, "llmsTxt": { "url": "https://developer.mapquest.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.161838807Z" }, "domain": { "domain": "mapquest.com", "registered": "1996-01-10", "source": "https://rdap.verisign.com/com/v1/domain/mapquest.com", "checkedAt": "2026-11-01T14:16:24.508888622Z" }, "mcpTools": { "url": "https://www.mapquestapi.com/mcp", "checkedAt": "2026-11-07T01:46:11.005976855Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:11.005976855Z" }, "updatedAt": "2026-11-07T18:20:37.631736415Z" } }, "answer": "Woosmap scores 59.4 (C) on agent readiness against MapQuest's 35.4 (F), and leads in 6 of 7 scored categories.", "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": 55, "category": "reliability", "leads": "woosmap", "name": "Reliability", "reasons": { "a": "Graded as a hosted service. No status page is linked from the developer site, the docs or the plans page (0). With no page there is no readable incident history (5). The reference marks endpoints 'Rate Limited Yes' and gives functional maximums (100 locations a batch, 50 a route, 25 a matrix) but no request-rate numbers (5). No 429, Retry-After or backoff guidance found (0). The Enterprise plan lists a service-level agreement, with no text published (3). The REST API is generally available and the MCP page calls the server production-ready (10).", "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": 23, "b": 78 } }, { "by": 34, "category": "schema", "leads": "woosmap", "name": "Schema \u0026 documentation", "reasons": { "a": "`https://developer.mapquest.com/openapi.json` describes the marketing site and has an empty `paths` object, so the product APIs have no machine-readable contract. The MCP tool definitions sit behind OAuth and were not read (0). `llms.txt` indexes every API with a one-line purpose (10). The reference states each endpoint's purpose and each parameter's effect, without when-not-to-use guidance (12). Parameter tables give ranges and allowed values in prose (8). Example requests and responses on each page, and status-code pages per API (12). Versions in the path (v1, v2, v4, v5) but no changelog (5).", "b": "OpenAPI 3.1 spec, version 1.46.3, with 47 paths across Localities, Stores, Distance, Datasets, Indoor, Map and what3words endpoints (25). llms.txt as a routing index, llms-full.txt and a Markdown twin of every page (10). llms.txt says which pages are authoritative for parameters and which explain products, and endpoint pages describe purpose, with little on when not to call one (15). Typed parameters from the spec with enums and required fields (13). The spec documents 400, 401, 402, 403, 404, 409, 422 and 429 responses, and pages carry examples (13). The spec is versioned, but no public changelog or release notes were found (developers.woosmap.com/changelog/ and /release-notes/ return 404) (5). 25+10+15+13+13+5 = 81." }, "scores": { "a": 47, "b": 81 } }, { "by": 23, "category": "transparency", "leads": "woosmap", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The only terms linked are System1's website terms of 26 February 2021, which allow personal, non-commercial use and do not mention the APIs. The plans page states the storage rule (5). The System1 group privacy policy of 5 July 2023 gives no retention periods and describes sale and sharing of personal information, while the plans page says 'we don't collect or sell user data' (8). No deprecation policy. Dated notices exist from 2018 only (5). The policy names categories of service providers, with no list or locations. The geocoding docs name TomTom for international queries (3).", "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": 31, "b": 54 } }, { "by": 16, "category": "ergonomics", "leads": "woosmap", "name": "Agent ergonomics", "reasons": { "a": "The MCP page names 13 tools. Their definitions were not read, so context cost is scored from the count and from REST controls such as `maxResults`, `thumbMaps=false` and `outFormat` (15). Place search pages with `pageSize` 1 to 50 and filters by category, circle, bounding box or corridor (16). Status codes are documented, with geocoding and directions errors carried in the response body and problem+json on the Account API (12). Most calls read and are safe to retry. Data Manager writes have no idempotency key, and MCP annotations were not read (10). Geocoding needs only `key` and `location`. The only current SDKs are browser libraries (7).", "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": 60, "b": 76 } }, { "by": 15, "category": "security", "leads": "woosmap", "name": "Security \u0026 auth", "reasons": { "a": "REST uses API keys, several per account, created in the dashboard or by API. The MCP server uses OAuth with one scope, `mcp:tools`. That earns 20, less 10 because the `key` query parameter is the documented way to send the secret (10). No key scopes, referrer or IP restrictions, or read-only mode found in the docs (3). Place and address text is returned with no prompt-injection guidance (7). The usage endpoint reports transactions by key, service and hour (8). No security.txt, disclosure policy, bug bounty or certification found (0).", "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": 28, "b": 43 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MapQuest (System1)", "b": "WOOSMAP SAS", "name": "Vendor" }, { "a": "https://www.mapquestapi.com", "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": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. No API terms were found published without a login", "b": "none", "name": "Licence" }, { "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-07-16", "b": "none", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "2024-07-01", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "2.8/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Woosmap scores 59.4 (C) on agent readiness against MapQuest's 35.4 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, MapQuest or Woosmap?" }, { "answer": "MapQuest takes an API key or an OAuth sign-in. Woosmap needs an API key.", "question": "Do MapQuest and Woosmap need an API key?" }, { "answer": "Yes. MapQuest has a hosted endpoint at https://www.mapquestapi.com and Woosmap at https://api.woosmap.com/mcp.", "question": "Can an agent call MapQuest and Woosmap without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "slug": "mapquest", "watchFor": "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only" }, { "aheadOn": [ "Reliability, 78 against 23", "Schema \u0026 documentation, 81 against 47", "Agent ergonomics, 76 against 60", "Security \u0026 auth, 43 against 28", "Transparency \u0026 trust, 54 against 31" ], "also": [ "Free to start without a card" ], "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": { "mapquest": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 35.5, "fromGrade": "F", "to": 35.4, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.4, "from": 35.1, "fromGrade": "F", "to": 35.5, "toGrade": "F" } ], "woosmap": null }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.json", "title": "Amazon Location Service vs MapQuest", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest" }, { "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-mapquest.json", "title": "ArcGIS Location Platform vs MapQuest", "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest" }, { "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-mapquest.json", "title": "Azure Maps vs MapQuest", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest" }, { "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-mapquest.json", "title": "Geoapify Location Platform + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest" }, { "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-mapquest.json", "title": "Geocodio vs MapQuest", "url": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest" }, { "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-mapquest.json", "title": "Google Maps Platform + Grounding Lite MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest" }, { "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-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-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-mapquest.json", "title": "LocationIQ vs MapQuest", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest" }, { "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-mapquest.json", "title": "Mapbox APIs + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest" }, { "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-maptiler.json", "title": "MapQuest vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/mapquest-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.json", "title": "MapQuest vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/mapquest-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim.json", "title": "MapQuest vs Nominatim", "url": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-opencage.json", "title": "MapQuest vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapquest-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-radar.json", "title": "MapQuest vs Radar", "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json", "title": "MapQuest vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "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": 55, "edge": "woosmap", "key": "reliability", "mapquest": 23, "name": "Reliability", "weight": 16, "woosmap": 78 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 34, "edge": "woosmap", "key": "schema", "mapquest": 47, "name": "Schema \u0026 documentation", "weight": 13, "woosmap": 81 }, { "by": 16, "edge": "woosmap", "key": "ergonomics", "mapquest": 60, "name": "Agent ergonomics", "weight": 13, "woosmap": 76 }, { "by": 15, "edge": "woosmap", "key": "security", "mapquest": 28, "name": "Security \u0026 auth", "weight": 14, "woosmap": 43 }, { "by": 0, "edge": "", "key": "payments", "mapquest": 30, "name": "Payments \u0026 pricing", "weight": 10, "woosmap": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "woosmap", "key": "maintenance", "mapquest": 23, "name": "Maintenance \u0026 community", "weight": 7, "woosmap": 26 }, { "by": 23, "edge": "woosmap", "key": "transparency", "mapquest": 31, "name": "Transparency \u0026 trust", "weight": 7, "woosmap": 54 } ], "summary": "Woosmap scores 59.4 (C) on agent readiness against MapQuest's 35.4 (F), and leads in 6 of 7 scored categories. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "mapquest": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.", "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/mapquest-vs-woosmap", "json": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap.min.md" }, "markdown": "Woosmap scores 59.4 (C) on agent readiness against MapQuest's 35.4 (F), and leads in 6 of 7 scored categories. Both do geocoding.\n\n- MapQuest: grade F, 35.4/100, rank #1373 of 1486. Markdown https://www.anchorterminal.com/tools/mapquest.md · JSON https://www.anchorterminal.com/api/v1/tools/mapquest.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### MapQuest (F)\n\nGood for: An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.\n\nWatch for: No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only\n\n### Woosmap (C)\n\nGood for: Store locators, address autocomplete and distance for retail and logistics teams that keep their own location data in the platform, with an MCP server for agents.\n\nAhead on:\n- Reliability, 78 against 23\n- Schema \u0026 documentation, 81 against 47\n- Agent ergonomics, 76 against 60\n- Security \u0026 auth, 43 against 28\n- Transparency \u0026 trust, 54 against 31\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No public changelog or release notes for the APIs\n\n\n## Why the edge\n\n### Reliability: Woosmap +55\n\n- MapQuest (23): Graded as a hosted service. No status page is linked from the developer site, the docs or the plans page (0). With no page there is no readable incident history (5). The reference marks endpoints 'Rate Limited Yes' and gives functional maximums (100 locations a batch, 50 a route, 25 a matrix) but no request-rate numbers (5). No 429, Retry-After or backoff guidance found (0). The Enterprise plan lists a service-level agreement, with no text published (3). The REST API is generally available and the MCP page calls the server production-ready (10).\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### Schema \u0026 documentation: Woosmap +34\n\n- MapQuest (47): `https://developer.mapquest.com/openapi.json` describes the marketing site and has an empty `paths` object, so the product APIs have no machine-readable contract. The MCP tool definitions sit behind OAuth and were not read (0). `llms.txt` indexes every API with a one-line purpose (10). The reference states each endpoint's purpose and each parameter's effect, without when-not-to-use guidance (12). Parameter tables give ranges and allowed values in prose (8). Example requests and responses on each page, and status-code pages per API (12). Versions in the path (v1, v2, v4, v5) but no changelog (5).\n- Woosmap (81): OpenAPI 3.1 spec, version 1.46.3, with 47 paths across Localities, Stores, Distance, Datasets, Indoor, Map and what3words endpoints (25). llms.txt as a routing index, llms-full.txt and a Markdown twin of every page (10). llms.txt says which pages are authoritative for parameters and which explain products, and endpoint pages describe purpose, with little on when not to call one (15). Typed parameters from the spec with enums and required fields (13). The spec documents 400, 401, 402, 403, 404, 409, 422 and 429 responses, and pages carry examples (13). The spec is versioned, but no public changelog or release notes were found (developers.woosmap.com/changelog/ and /release-notes/ return 404) (5). 25+10+15+13+13+5 = 81.\n\n### Transparency \u0026 trust: Woosmap +23\n\n- MapQuest (31): Closed service. The only terms linked are System1's website terms of 26 February 2021, which allow personal, non-commercial use and do not mention the APIs. The plans page states the storage rule (5). The System1 group privacy policy of 5 July 2023 gives no retention periods and describes sale and sharing of personal information, while the plans page says 'we don't collect or sell user data' (8). No deprecation policy. Dated notices exist from 2018 only (5). The policy names categories of service providers, with no list or locations. The geocoding docs name TomTom for international queries (3).\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### Agent ergonomics: Woosmap +16\n\n- MapQuest (60): The MCP page names 13 tools. Their definitions were not read, so context cost is scored from the count and from REST controls such as `maxResults`, `thumbMaps=false` and `outFormat` (15). Place search pages with `pageSize` 1 to 50 and filters by category, circle, bounding box or corridor (16). Status codes are documented, with geocoding and directions errors carried in the response body and problem+json on the Account API (12). Most calls read and are safe to retry. Data Manager writes have no idempotency key, and MCP annotations were not read (10). Geocoding needs only `key` and `location`. The only current SDKs are browser libraries (7).\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### Security \u0026 auth: Woosmap +15\n\n- MapQuest (28): REST uses API keys, several per account, created in the dashboard or by API. The MCP server uses OAuth with one scope, `mcp:tools`. That earns 20, less 10 because the `key` query parameter is the documented way to send the secret (10). No key scopes, referrer or IP restrictions, or read-only mode found in the docs (3). Place and address text is returned with no prompt-injection guidance (7). The usage endpoint reports transactions by key, service and hour (8). No security.txt, disclosure policy, bug bounty or certification found (0).\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## Score by category\n\n| Category | Weight | MapQuest | Woosmap | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 78 | Woosmap +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 47 | 81 | Woosmap +34 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 76 | Woosmap +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 28 | 43 | Woosmap +15 |\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) | 23 | 26 | Woosmap +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 31 | 54 | Woosmap +23 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **35.4 · F** | **59.4 · C** | |\n\n## Facts side by side\n\n| Fact | MapQuest | Woosmap |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MapQuest (System1) | WOOSMAP SAS |\n| Hosted endpoint | `https://www.mapquestapi.com` | `https://api.woosmap.com/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service. No API terms were found published without a login | none |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-07-16 | none |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | 2024-07-01 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Agent reviews | 2.8/5 (4) | none |\n\n## How the scores have moved\n\n### MapQuest\n\n- -0.1 on 28 October 2026: correction\n- +0.4 on 27 October 2026: checklist\n\n### Woosmap\n\nNo score change since it was listed.\n\n## Verdicts\n\n**MapQuest.** One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.\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### MapQuest\n\n1. Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use\n2. Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs\n3. Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body\n4. Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small\n5. Do not store or cache geocodes on a monthly or pay-as-you-go plan\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, MapQuest or Woosmap?\n\nWoosmap scores 59.4 (C) on agent readiness against MapQuest's 35.4 (F), and leads in 6 of 7 scored categories.\n\n### Do MapQuest and Woosmap need an API key?\n\nMapQuest takes an API key or an OAuth sign-in. Woosmap needs an API key.\n\n### Can an agent call MapQuest and Woosmap without installing anything?\n\nYes. MapQuest has a hosted endpoint at https://www.mapquestapi.com and Woosmap at https://api.woosmap.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mapquest-vs-woosmap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mapquest-vs-woosmap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mapquest\", \"b\": \"woosmap\"}`. From a terminal: `anchor compare mapquest woosmap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mapquest.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json\n\n## Other comparisons with MapQuest or Woosmap\n\n- [Amazon Location Service vs MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.md)\n- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)\n- [ArcGIS Location Platform vs MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)\n- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)\n- [Azure Maps vs MapQuest](https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.md)\n- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)\n- [Geoapify Location Platform + MCP vs MapQuest](https://www.anchorterminal.com/compare/geoapify-vs-mapquest.md)\n- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)\n- [Geocodio vs MapQuest](https://www.anchorterminal.com/compare/geocodio-vs-mapquest.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)\n- [Google Maps Platform + Grounding Lite MCP vs MapQuest](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest.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 MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md)\n- [LocationIQ vs MapQuest](https://www.anchorterminal.com/compare/locationiq-vs-mapquest.md)\n- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md)\n- [Mapbox APIs + MCP vs MapQuest](https://www.anchorterminal.com/compare/mapbox-vs-mapquest.md)\n- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md)\n- [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md)\n- [MapQuest vs NextBillion.ai](https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.md)\n- [MapQuest vs Nominatim](https://www.anchorterminal.com/compare/mapquest-vs-nominatim.md)\n- [MapQuest vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapquest-vs-opencage.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.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": "MapQuest vs Woosmap", "url": "" } ], "description": "Woosmap scores 59.4 (C) to MapQuest's 35.4 (F) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MapQuest F 35.4", "Woosmap C 59.4", "scores" ], "h1": "MapQuest vs Woosmap", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mapquest-vs-woosmap", "published": "2026-10-01", "section": "tools", "title": "MapQuest vs Woosmap for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap" }, "tokens": { "markdown": 4300, "slim": 2380 }, "version": 1 }