{ "data": { "a": { "slug": "maptiler", "name": "MapTiler Cloud", "vendor": "MapTiler AG", "vendorUrl": "https://www.maptiler.com", "kind": "http-api", "category": "maps", "summary": "MapTiler Cloud is a hosted maps platform from MapTiler AG in Switzerland. Its read-only REST APIs serve map styles, vector and raster tiles, static maps, forward and reverse geocoding, IP geolocation, elevation, coordinate transforms and weather data.", "url": "https://www.anchorterminal.com/tools/maptiler", "markdownUrl": "https://www.anchorterminal.com/tools/maptiler.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/maptiler.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/maptiler.json", "dns": "maptiler.grade.anchorterminal.com", "repo": "https://github.com/maptiler/maptiler-client-js", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@maptiler/client" }, { "registry": "npm", "name": "@maptiler/sdk" } ], "auth": "api-key", "authNotes": "API key from the MapTiler Cloud account after a browser signup, always passed as the `key` query parameter. Keys can be limited to HTTP origins and a User-Agent substring and are managed through the Service API. From a backend, a service token can sign each request with a `signature` parameter instead. The Service API (uploads, tilesets, keys, analytics) needs a service token.", "pricing": "freemium", "pricingNotes": "Free plan with 100,000 API requests, 5,000 sessions and 1,000 search sessions a month, no card, for testing and non-commercial use; service pauses at the limit. Flex is $30 a month with 500,000 requests, then $0.15 per 1,000 requests and $2.50 per 1,000 search sessions. Custom contracts carry a 99.9% SLA.", "priceSummary": "$0.15 / 1k req", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, OpenAPI spec, llms.txt or pricing page (checked 2026-11-06). Paid plans are billed by FastSpring.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 114682, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.maptiler.com/cloud/api/", "llmsTxt": "https://docs.maptiler.com/llms.txt", "openapi": "https://docs.maptiler.com/_data/cloud/api/openapi.yml", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.tiles", "data.weather" ], "tags": [ "hosted", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "agent-skills", "typescript", "status-page", "security-txt", "iso27001", "eu", "eu-region", "sla", "closed-source" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 62.1, "grade": "B", "agentReady": false, "rank": 576, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 70, "payments": 40, "reliability": 43, "schema": 79, "security": 64, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.", "bestFor": "Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.", "strengths": [ "OpenAPI 3.1.0 spec, llms.txt, llms-full.txt and a Markdown version of every docs page", "Geocoding results may be bulk downloaded and used outside the service with attribution", "Keys can be restricted by origin and User-Agent, and service tokens can sign requests instead", "ISO/IEC 27001:2022 certification, security.txt and a vulnerability disclosure policy", "EU-only endpoint at api.maptiler.eu and hosting mainly in Switzerland and the EEA" ], "weaknesses": [ "The API key is always sent as a query parameter", "No routing, directions or matrix API", "No per-second rate limit, 429 behaviour or retry guidance found in the documentation", "The free plan is for testing and non-commercial use only, and pauses at its monthly limit", "Official clients are JavaScript and TypeScript only" ], "agentNotes": [ "Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL", "Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address", "Use api.maptiler.eu when the user's requests must stay in the EU", "Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt", "Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.1 } ], "editorialScores": { "ergonomics": 70, "maintenance": 70, "payments": 40, "reliability": 43, "schema": 79, "security": 64, "transparency": 64 }, "provenanceScore": 96, "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": { "install": "npm install @maptiler/client", "http": "curl \"https://api.maptiler.com/geocoding/Zurich.json?language=en\u0026limit=3\u0026key=$MAPTILER_API_KEY\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/maptiler" }, "area": "everyday", "unitPrices": [ { "item": "API requests over the Flex allowance", "unit": "1k-requests", "usd": 0.15, "note": "Flex includes 500,000 a month" }, { "item": "Search sessions over the Flex allowance", "unit": "1k-requests", "usd": 2.5, "note": "Priced per 1,000 search sessions through MapTiler SDK JS" }, { "item": "Flex plan", "unit": "month", "usd": 30, "note": "Extra usage billed monthly" } ], "provenance": { "legalEntity": "MapTiler AG", "domain": "maptiler.com", "domainRegistered": "2008-08-08", "endpointOnVendorDomain": true, "terms": "https://www.maptiler.com/terms/", "privacy": "https://www.maptiler.com/privacy-policy/", "statusPage": "https://status.maptiler.com", "changelog": "https://docs.maptiler.com/updates/", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The general terms name MapTiler AG, Zugerstrasse 22, 6314 Unterägeri, Switzerland, under Swiss law with courts in Zug.", "security.txt at www.maptiler.com/.well-known/security.txt names sysadmin@maptiler.com, a PGP key and a signature, and has no Expires field.", "status.maptiler.com is a StatusCake public report whose data loads from app.statuscake.com. That host's robots.txt answered with a redirect, so it wasn't fetched and no uptime or incident history was read.", "RDAP gives maptiler.com a registration date of 8 August 2008.", "No clause on automated access to the website was found in the general terms. robots.txt on www.maptiler.com and docs.maptiler.com allows all agents apart from a few paths." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/maptiler.json", "live": { "slug": "maptiler", "vendorStatus": { "page": "https://status.maptiler.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:02.124798696Z" }, "versions": [ { "registry": "github", "name": "maptiler/maptiler-client-js", "version": "v3.1.0", "released": "2026-10-02", "seenAt": "2026-11-06T23:42:38.646681081Z" }, { "registry": "npm", "name": "@maptiler/client", "version": "3.1.0", "seenAt": "2026-11-06T23:42:36.419318643Z" }, { "registry": "npm", "name": "@maptiler/sdk", "version": "4.2.1", "seenAt": "2026-11-06T23:42:37.315182633Z" } ], "githubStars": 25, "npmWeekly": 114682, "securityTxt": { "url": "https://maptiler.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T15:59:35.51300876Z" }, "llmsTxt": { "url": "https://docs.maptiler.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.151624353Z" }, "pages": [ { "url": "https://docs.maptiler.com/updates/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:56.724195464Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1152e8fe8b9d" }, { "url": "https://www.maptiler.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:21.154658791Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "46d3f1544780" }, { "url": "https://www.maptiler.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:23.29013826Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fc740f21aa9f" } ], "updatedAt": "2026-11-07T15:59:35.51300876Z" } }, "answer": "MapTiler Cloud scores 62.1 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics and maintenance \u0026 community.", "b": { "slug": "tomtom", "name": "TomTom Maps APIs + MCP", "vendor": "TomTom", "vendorUrl": "https://developer.tomtom.com", "kind": "http-api", "category": "maps", "summary": "Search, Geocoding and Reverse Geocoding, Routing, Matrix Routing, Reachable Range, EV routing and live traffic, plus map tiles.", "url": "https://www.anchorterminal.com/tools/tomtom", "markdownUrl": "https://www.anchorterminal.com/tools/tomtom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tomtom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tomtom.json", "dns": "tomtom.grade.anchorterminal.com", "repo": "https://github.com/tomtom-international/tomtom-mcp", "license": "Apache-2.0 (MCP server)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.tomtom.com", "packages": [ { "registry": "npm", "name": "@tomtom-org/tomtom-mcp" } ], "auth": "api-key", "authNotes": "One API key, passed as the key query parameter on REST calls. The hosted MCP takes it in a tomtom-api-key header, and OAuth deployments must set OAUTH_AUDIENCE since 1.6.13. Since 1.6.11 every tool runs on the Orbis backend; the MAPS variable and the tomtom-maps-backend header are no longer read.", "pricing": "freemium", "pricingNotes": "Free monthly allowance with no card. 2,500 Search, 20,000 Geocoding, 20,000 Routing, 2,500 Matrix Routing, 200,000 vector and 200,000 raster tiles and 20,000 non-tile map requests. Past that it's pay as you grow in euros at volume tiers, worked out by an estimator on the pricing page. The per-request rates sit behind per-API detail links we couldn't read, so no rate is quoted here (https://docs.tomtom.com/pricing).", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": 55, "npmWeekly": 996, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.tomtom.com", "llmsTxt": "https://docs.tomtom.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.places", "geo.routing", "geo.tiles" ], "tags": [ "hosted", "mcp", "official", "typescript", "free-tier", "no-card", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 45.9, "grade": "E", "agentReady": false, "rank": 1185, "ranked": true, "rankOf": 1510, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 15, "schema": 71, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": -6, "negativeNotes": [ "2026-10-05 to 2026-10-22. `@tomtom-org/tomtom-mcp` 1.6.11, 1.6.12 and 1.6.13, patch releases, carry changes marked BREAKING in the changelog with no earlier dated notice found. They removed the Genesis backend, the MAPS variable and the tomtom-maps-backend header, tomtom-static-map, tomtom-waypoint-routing, tomtom-reachable-range and tomtom-ev-routing, replaced offset paging with cursors and changed 75 POI category codes. A breaking change in a minor or patch release without notice (-3). https://github.com/tomtom-international/tomtom-mcp/blob/main/CHANGELOG.md", "2026-10-05 and 2026-10-22. 1.6.11 fixes tomtom-reachable-range returning the caller's TomTom API key in full responses, and 1.6.13 stops OAuth deployments accepting tokens issued for other TomTom applications. No advisory was found for either. Released fixes of the package's own described flaws with no advisory, folded (-3). https://github.com/tomtom-international/tomtom-mcp/blob/main/CHANGELOG.md" ], "verdict": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.", "bestFor": "Drive planning with live traffic, EV charging and reachable range.", "strengths": [ "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month", "Live traffic, EV charging search and search along a route as MCP tools", "MCP tools annotated read-only, idempotent and non-destructive, with typed errors that tell a missing key from a refused account", "Eight MCP releases between 15 September and 2 November 2026, with Veracode scanning and end-to-end tests in CI", "HackerOne disclosure programme with a 3 business day first response" ], "weaknesses": [ "Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified", "The ServiceNow status page disallows every path in robots.txt, so no incident history could be read", "MCP patch releases 1.6.11 to 1.6.13 removed tools, inputs and the older backend, marked breaking with no earlier notice", "Paid prices only through a euro estimator", "Only 2,500 free Search and Matrix calls a month" ], "agentNotes": [ "Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address", "Pin `@tomtom-org/tomtom-mcp` to a version, since patch releases have removed tools and changed inputs", "Page search results with `cursor` and the previous response's `nextCursor`, not `ofs`, from 1.6.12", "Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key", "Redact the key parameter before logging REST URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 86, "payments": 25, "reliability": 15, "schema": 71, "security": 51, "transparency": 41 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.tomtom.com/search/2/geocode/10%20Downing%20Street%2C%20London.json?limit=1\u0026key=$TOMTOM_API_KEY\"", "claudeCode": "claude mcp add --transport http tomtom https://mcp.tomtom.com/maps --header \"tomtom-api-key: $TOMTOM_API_KEY\"", "config": { "mcpServers": { "tomtom": { "args": [ "-y", "@tomtom-org/tomtom-mcp@latest" ], "command": "npx", "env": { "TOMTOM_API_KEY": "${TOMTOM_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/tomtom" }, "area": "everyday", "provenance": { "legalEntity": "TomTom International BV", "domain": "tomtom.com", "domainRegistered": "1996-02-23", "endpointOnVendorDomain": true, "terms": "https://docs.tomtom.com/legal/terms-and-conditions", "privacy": "https://www.tomtom.com/privacy/", "statusPage": "https://tomtom.service-now.com/status", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The privacy policy names TomTom International BV and was last edited 1 August 2024, per the 2 October check. Subprocessors and storage locations are on https://www.tomtom.com/en-gb/privacy/more-information/.", "The developer terms page still renders client-side on 4 November 2026, and developer.tomtom.com/legal redirects to it, so storage and caching rules are unverified. TomTom's Terms of Use (effective 1 September 2025) and acceptable use policy cover all TomTom websites.", "www.tomtom.com/.well-known/security.txt returned 404 per the 30 September check. Vulnerabilities go to TomTom's HackerOne programme, per the security policy in the tomtom-international GitHub organisation.", "The status page is a ServiceNow page at tomtom.service-now.com, whose robots.txt disallows every path on 4 November 2026.", "A deprecation policy page is linked from docs.tomtom.com/llms.txt but rendered client-side, and its .md twin returned 404, per the 1 October check." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tomtom.json", "live": { "slug": "tomtom", "probe": { "target": "https://api.tomtom.com", "method": "get", "lastAt": "2026-11-07T19:22:41.075542175Z", "lastOk": true, "lastStatus": 200, "lastMs": 286, "authRequired": false, "uptime24h": 100, "uptime30d": 99.96, "p50ms24h": 202, "p95ms24h": 498, "samples24h": 238, "samples30d": 7920, "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": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 247 }, { "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": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://tomtom.service-now.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:53.259050511Z" }, "versions": [ { "registry": "github", "name": "tomtom-international/tomtom-mcp", "version": "v1.6.15", "released": "2026-11-02", "seenAt": "2026-11-07T00:12:31.820004932Z" }, { "registry": "npm", "name": "@tomtom-org/tomtom-mcp", "version": "1.6.15", "seenAt": "2026-11-07T00:12:30.983981983Z" } ], "githubStars": 59, "npmWeekly": 533, "securityTxt": { "url": "https://tomtom.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:35.80240856Z" }, "llmsTxt": { "url": "https://docs.tomtom.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:10.63321814Z" }, "domain": { "domain": "tomtom.com", "registered": "1996-02-23", "source": "https://rdap.verisign.com/com/v1/domain/tomtom.com", "checkedAt": "2026-11-01T14:08:40.010831658Z" }, "pages": [ { "url": "https://docs.tomtom.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:08:24.436245345Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f426a4be50f" }, { "url": "https://www.tomtom.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:35:50.482210619Z", "changedAt": "2026-10-08T18:31:01.446679763Z", "fingerprint": "b77d548785dc" }, { "url": "https://docs.tomtom.com/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:08:22.338954308Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "68f5b7cd1e5c" } ], "mcpTools": { "url": "https://mcp.tomtom.com/maps", "checkedAt": "2026-11-07T01:48:48.000289783Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:48.000289783Z" }, "github": { "repo": "tomtom-international/tomtom-mcp", "checkedAt": "2026-11-02T09:32:23.866567335Z", "stars": 59, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T09:12:05Z", "openIssues": 6, "openPRs": 9, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-02T08:40:13Z" }, "replies": { "sampled": 10, "unanswered": 6, "medianDays": 10.4 } }, "updatedAt": "2026-11-07T19:22:41.075542175Z" } }, "edges": [ { "by": 28, "category": "reliability", "leads": "maptiler", "name": "Reliability", "reasons": { "a": "Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43.", "b": "TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15." }, "scores": { "a": 43, "b": 15 } }, { "by": 22, "category": "transparency", "leads": "maptiler", "name": "Transparency \u0026 trust", "reasons": { "a": "Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64.", "b": "Closed APIs with an Apache-2.0 MCP server. The developer terms page still renders client-side on 4 November, and TomTom's acceptable use policy (linked from its Terms of Use of 1 September 2025) bars data mining, robots and scraping on all TomTom websites, so the privacy and deprecation pages weren't re-read. Licence clarity 10, data handling 11 of 30, deprecation 8 and subprocessors 12 of 20 stand per the 2 October check, not re-read on 4 November. 10+11+8+12 = 41." }, "scores": { "a": 80, "b": 58 } }, { "by": 16, "category": "maintenance", "leads": "tomtom", "name": "Maintenance \u0026 community", "reasons": { "a": "@maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70.", "b": "MCP v1.6.15 on 2 November 2026 (30). Eight tags since 6 August, v1.6.8 (15 September) to v1.6.15 (2 November) (20). Pull requests from several maintainers merged up to 3 November 2026. We couldn't see issue reply times from git (18, kept). The package is at 1.6.15 in its repository; the 30 September note that it wasn't in the official MCP registry came from the registry's JSON API and is struck (8, kept). CI runs type checks, lint, build, end-to-end tests and a Veracode scan, with dependabot (10). 30+20+18+8+10 = 86." }, "scores": { "a": 70, "b": 86 } }, { "by": 15, "category": "payments", "leads": "maptiler", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40.", "b": "No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25." }, "scores": { "a": 40, "b": 25 } }, { "by": 13, "category": "security", "leads": "maptiler", "name": "Security \u0026 auth", "reasons": { "a": "Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64.", "b": "API keys from the developer portal, limited to the products selected for them, which earns 25. Less 10 because REST calls take the key as the key query parameter. The hosted MCP takes a tomtom-api-key header, and the source carries OAuth with an audience check that 1.6.13 made mandatory for OAuth deployments (15). Keys can be limited by product and every tool reads (16). Results include POI names and traffic incident text with no prompt-injection guidance. An app-only tool, tomtom-get-api-key, returns the raw key to the map app; since 1.6.12 clients that render no apps don't receive it (6, kept). We didn't find per-call logs or usage reporting we could read (0). HackerOne disclosure programme with a 3 business day first response in the organisation's SECURITY.md, Veracode scanning in CI, and no security.txt per the 30 September check (14, kept). 15+16+6+0+14 = 51." }, "scores": { "a": 64, "b": 51 } }, { "by": 8, "category": "schema", "leads": "maptiler", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79.", "b": "No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71." }, "scores": { "a": 79, "b": 71 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MapTiler AG", "b": "TomTom", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.tomtom.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "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": "Apache-2.0 (MCP server)", "name": "Licence" }, { "a": "none", "b": "13", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-02", "b": "2026-11-02", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "115k npm/wk", "b": "55 stars, 996 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "MapTiler Cloud scores 62.1 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, MapTiler Cloud or TomTom Maps APIs + MCP?" }, { "answer": "Both need an API key.", "question": "Do MapTiler Cloud and TomTom Maps APIs + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for MapTiler Cloud. TomTom Maps APIs + MCP has a hosted endpoint at https://api.tomtom.com.", "question": "Can an agent call MapTiler Cloud and TomTom Maps APIs + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 43 against 15", "Schema \u0026 documentation, 79 against 71", "Security \u0026 auth, 64 against 51", "Payments \u0026 pricing, 40 against 25", "Transparency \u0026 trust, 80 against 58" ], "also": [ "No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them" ], "goodFor": "Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.", "slug": "maptiler", "watchFor": "The API key is always sent as a query parameter" }, { "aheadOn": [ "Agent ergonomics, 78 against 70", "Maintenance \u0026 community, 86 against 70" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Drive planning with live traffic, EV charging and reachable range.", "slug": "tomtom", "watchFor": "Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified" } ], "history": { "maptiler": null, "tomtom": [ { "causes": [ "product", "evidence" ], "date": "2026-11-04", "delta": -9, "from": 54.9, "fromGrade": "C", "to": 45.9, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 55.1, "fromGrade": "C", "to": 54.9, "toGrade": "C" } ] }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.json", "title": "Amazon Location Service vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.json", "title": "Amazon Location Service vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-maptiler.json", "title": "ArcGIS Location Platform vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/arcgis-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom.json", "title": "ArcGIS Location Platform vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/arcgis-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.json", "title": "Azure Maps vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.json", "title": "Azure Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-maptiler.json", "title": "Geoapify Location Platform + MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geoapify-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom.json", "title": "Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geoapify-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler.json", "title": "Geocodio vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom.json", "title": "Geocodio vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.json", "title": "Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.json", "title": "Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.json", "title": "HERE Location Services vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.json", "title": "HERE Location Services vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler.json", "title": "LocationIQ vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/locationiq-vs-maptiler" }, { "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-maptiler.json", "title": "Mapbox APIs + MCP vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/mapbox-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom.json", "title": "Mapbox APIs + MCP vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapbox-vs-tomtom" }, { "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-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-nextbillion.json", "title": "MapTiler Cloud vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/maptiler-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim.json", "title": "MapTiler Cloud vs Nominatim", "url": "https://www.anchorterminal.com/compare/maptiler-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-opencage.json", "title": "MapTiler Cloud vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/maptiler-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-radar.json", "title": "MapTiler Cloud vs Radar", "url": "https://www.anchorterminal.com/compare/maptiler-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.json", "title": "MapTiler Cloud vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap.json", "title": "MapTiler Cloud vs Woosmap", "url": "https://www.anchorterminal.com/compare/maptiler-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom.json", "title": "Nominatim vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/nominatim-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-tomtom.json", "title": "OpenCage Geocoding API vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/opencage-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/radar-vs-tomtom.json", "title": "Radar vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/radar-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.json", "title": "Stadia Maps vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap.json", "title": "TomTom Maps APIs + MCP vs Woosmap", "url": "https://www.anchorterminal.com/compare/tomtom-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.json", "title": "NextBillion.ai vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-tomtom" } ], "panel": null, "scores": [ { "by": 28, "edge": "maptiler", "key": "reliability", "maptiler": 43, "name": "Reliability", "tomtom": 15, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "maptiler", "key": "schema", "maptiler": 79, "name": "Schema \u0026 documentation", "tomtom": 71, "weight": 13 }, { "by": 8, "edge": "tomtom", "key": "ergonomics", "maptiler": 70, "name": "Agent ergonomics", "tomtom": 78, "weight": 13 }, { "by": 13, "edge": "maptiler", "key": "security", "maptiler": 64, "name": "Security \u0026 auth", "tomtom": 51, "weight": 14 }, { "by": 15, "edge": "maptiler", "key": "payments", "maptiler": 40, "name": "Payments \u0026 pricing", "tomtom": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "tomtom", "key": "maintenance", "maptiler": 70, "name": "Maintenance \u0026 community", "tomtom": 86, "weight": 7 }, { "by": 22, "edge": "maptiler", "key": "transparency", "maptiler": 80, "name": "Transparency \u0026 trust", "tomtom": 58, "weight": 7 } ], "summary": "MapTiler Cloud scores 62.1 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics and maintenance \u0026 community. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "maptiler": "MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.", "tomtom": "No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom", "json": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom.min.md" }, "markdown": "MapTiler Cloud scores 62.1 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics and maintenance \u0026 community. Both do geocoding.\n\n- MapTiler Cloud: grade B, 62.1/100, rank #576 of 1510. Markdown https://www.anchorterminal.com/tools/maptiler.md · JSON https://www.anchorterminal.com/api/v1/tools/maptiler.json\n- TomTom Maps APIs + MCP: grade E, 45.9/100, rank #1185 of 1510. Markdown https://www.anchorterminal.com/tools/tomtom.md · JSON https://www.anchorterminal.com/api/v1/tools/tomtom.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### MapTiler Cloud (B)\n\nGood for: Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency.\n\nAhead on:\n- Reliability, 43 against 15\n- Schema \u0026 documentation, 79 against 71\n- Security \u0026 auth, 64 against 51\n- Payments \u0026 pricing, 40 against 25\n- Transparency \u0026 trust, 80 against 58\n\nAlso in its favour:\n- No incidents deducted, where TomTom Maps APIs + MCP loses 6 points for them\n\nWatch for: The API key is always sent as a query parameter\n\n### TomTom Maps APIs + MCP (E)\n\nGood for: Drive planning with live traffic, EV charging and reachable range.\n\nAhead on:\n- Agent ergonomics, 78 against 70\n- Maintenance \u0026 community, 86 against 70\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Terms, rate limits and deprecation policy couldn't be read, so storage rules and notice periods are unverified\n\n\n## Why the edge\n\n### Reliability: MapTiler Cloud +28\n\n- MapTiler Cloud (43): Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43.\n- TomTom Maps APIs + MCP (15): TomTom's API status page sits on tomtom.service-now.com, whose robots.txt disallows every path on 4 November, so the earlier status readings are struck (0). With no history we may read, the record scores 5. No published QPS limits or 429 guidance were found on the docs pages we read on 1 October; TomTom's acceptable use policy now bars robots from its websites, so they weren't re-read (0). The MCP maps a 429 to a typed rate-limit error with a message, and we found nothing on Retry-After (5, the earlier partial kept). No SLA found (0). Orbis APIs went GA on 8 July 2026, but the remote MCP server is in public preview and the README says some Orbis and EV services may not be enabled on every account (5, kept). 0+5+0+5+0+5 = 15.\n\n### Transparency \u0026 trust: MapTiler Cloud +22\n\n- MapTiler Cloud (80): Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64.\n- TomTom Maps APIs + MCP (58): Closed APIs with an Apache-2.0 MCP server. The developer terms page still renders client-side on 4 November, and TomTom's acceptable use policy (linked from its Terms of Use of 1 September 2025) bars data mining, robots and scraping on all TomTom websites, so the privacy and deprecation pages weren't re-read. Licence clarity 10, data handling 11 of 30, deprecation 8 and subprocessors 12 of 20 stand per the 2 October check, not re-read on 4 November. 10+11+8+12 = 41.\n\n### Maintenance \u0026 community: TomTom Maps APIs + MCP +16\n\n- MapTiler Cloud (70): @maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70.\n- TomTom Maps APIs + MCP (86): MCP v1.6.15 on 2 November 2026 (30). Eight tags since 6 August, v1.6.8 (15 September) to v1.6.15 (2 November) (20). Pull requests from several maintainers merged up to 3 November 2026. We couldn't see issue reply times from git (18, kept). The package is at 1.6.15 in its repository; the 30 September note that it wasn't in the official MCP registry came from the registry's JSON API and is struck (8, kept). CI runs type checks, lint, build, end-to-end tests and a Veracode scan, with dependabot (10). 30+20+18+8+10 = 86.\n\n### Payments \u0026 pricing: MapTiler Cloud +15\n\n- MapTiler Cloud (40): No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40.\n- TomTom Maps APIs + MCP (25): No x402, MPP or L402 (0). Free allowances are public, but the pricing page re-read on 2 October showed no paid rate as a number, only a euro estimator and a contact-sales link (5 of 20, kept). A no-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with Search and Matrix at 2,500 (20). Signup is a browser flow (0). The pricing page is on a host whose acceptable use policy now bars robots, so it wasn't re-read on 4 November. 0+5+20+0 = 25.\n\n### Security \u0026 auth: MapTiler Cloud +13\n\n- MapTiler Cloud (64): Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64.\n- TomTom Maps APIs + MCP (51): API keys from the developer portal, limited to the products selected for them, which earns 25. Less 10 because REST calls take the key as the key query parameter. The hosted MCP takes a tomtom-api-key header, and the source carries OAuth with an audience check that 1.6.13 made mandatory for OAuth deployments (15). Keys can be limited by product and every tool reads (16). Results include POI names and traffic incident text with no prompt-injection guidance. An app-only tool, tomtom-get-api-key, returns the raw key to the map app; since 1.6.12 clients that render no apps don't receive it (6, kept). We didn't find per-call logs or usage reporting we could read (0). HackerOne disclosure programme with a 3 business day first response in the organisation's SECURITY.md, Veracode scanning in CI, and no security.txt per the 30 September check (14, kept). 15+16+6+0+14 = 51.\n\n### Schema \u0026 documentation: MapTiler Cloud +8\n\n- MapTiler Cloud (79): OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79.\n- TomTom Maps APIs + MCP (71): No public OpenAPI that we found. The MCP's tools have Zod schemas with described fields (22). docs.tomtom.com/llms.txt indexes about 180 pages, many as .md, per the 2 October check, not re-read on 4 November (10). Tool descriptions are mostly one line, with little on when not to use a tool (12). Typed fields with constraints, and since 1.6.12 the search, routing and EV tools list their valid values from the maps-sdk (11, kept). We couldn't read the REST error reference. The MCP returns typed errors per status code, and since 1.6.13 tells a 401 from a 403 (8). Versioned REST paths; the MCP CHANGELOG.md has dated entries from 1.6.11 (5 October 2026) to 1.6.14 and says 1.1.1 to 1.6.10 have none (8, kept). 22+10+12+11+8+8 = 71.\n\n## Score by category\n\n| Category | Weight | MapTiler Cloud | TomTom Maps APIs + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 43 | 15 | MapTiler Cloud +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 71 | MapTiler Cloud +8 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 78 | TomTom Maps APIs + MCP +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 51 | MapTiler Cloud +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 25 | MapTiler Cloud +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 86 | TomTom Maps APIs + MCP +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 58 | MapTiler Cloud +22 |\n| Negative events | ≤15 | 0 | -6 | |\n| **Total** | | **62.1 · B** | **45.9 · E** | |\n\n## Facts side by side\n\n| Fact | MapTiler Cloud | TomTom Maps APIs + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MapTiler AG | TomTom |\n| Hosted endpoint | no (local only) | `https://api.tomtom.com` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Apache-2.0 (MCP server) |\n| Tools exposed | none | 13 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-02 | 2026-11-02 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | 115k npm/wk | 55 stars, 996 npm/wk |\n| Agent reviews | none | 3/5 (2) |\n\n## How the scores have moved\n\n### MapTiler Cloud\n\nNo score change since it was listed.\n\n### TomTom Maps APIs + MCP\n\n- -9.0 on 4 November 2026 (C to E): product, new evidence\n- -0.2 on 8 October 2026: checklist\n\n## Verdicts\n\n**MapTiler Cloud.** MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use.\n\n**TomTom Maps APIs + MCP.** No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month, with an official MCP server released about weekly. Terms, rate limits and the deprecation policy couldn't be read, the status page bars our reader, and MCP patch releases in October removed tools and inputs without notice.\n\n## Before you call either\n\n### MapTiler Cloud\n\n1. Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL\n2. Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address\n3. Use api.maptiler.eu when the user's requests must stay in the EU\n4. Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt\n5. Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution\n\n### TomTom Maps APIs + MCP\n\n1. Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address\n2. Pin `@tomtom-org/tomtom-mcp` to a version, since patch releases have removed tools and changed inputs\n3. Page search results with `cursor` and the previous response's `nextCursor`, not `ofs`, from 1.6.12\n4. Read a 403 as the account or key not covering the API, and don't retry it; a 401 means a missing or unknown key\n5. Redact the key parameter before logging REST URLs\n\n## Questions\n\n### Which is better for AI agents, MapTiler Cloud or TomTom Maps APIs + MCP?\n\nMapTiler Cloud scores 62.1 (B) on agent readiness against TomTom Maps APIs + MCP's 45.9 (E), and leads in 5 of 7 scored categories. TomTom Maps APIs + MCP leads on agent ergonomics and maintenance \u0026 community.\n\n### Do MapTiler Cloud and TomTom Maps APIs + MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call MapTiler Cloud and TomTom Maps APIs + MCP without installing anything?\n\nNo hosted endpoint is listed for MapTiler Cloud. TomTom Maps APIs + MCP has a hosted endpoint at https://api.tomtom.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/maptiler-vs-tomtom.json, and with the fewest tokens: https://www.anchorterminal.com/compare/maptiler-vs-tomtom.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"maptiler\", \"b\": \"tomtom\"}`. From a terminal: `anchor compare maptiler tomtom`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/maptiler.json and https://www.anchorterminal.com/api/v1/tools/tomtom.json\n\n## Other comparisons with MapTiler Cloud or TomTom Maps APIs + MCP\n\n- [Amazon Location Service vs MapTiler Cloud](https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.md)\n- [Amazon Location Service vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/amazon-location-vs-tomtom.md)\n- [ArcGIS Location Platform vs MapTiler Cloud](https://www.anchorterminal.com/compare/arcgis-vs-maptiler.md)\n- [ArcGIS Location Platform vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/arcgis-vs-tomtom.md)\n- [Azure Maps vs MapTiler Cloud](https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.md)\n- [Azure Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/azure-maps-vs-tomtom.md)\n- [Geoapify Location Platform + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/geoapify-vs-maptiler.md)\n- [Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geoapify-vs-tomtom.md)\n- [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md)\n- [Geocodio vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-tomtom.md)\n- [Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.md)\n- [Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/google-maps-platform-vs-tomtom.md)\n- [HERE Location Services vs MapTiler Cloud](https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs MapTiler Cloud](https://www.anchorterminal.com/compare/locationiq-vs-maptiler.md)\n- [LocationIQ vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/locationiq-vs-tomtom.md)\n- [Mapbox APIs + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapbox-vs-maptiler.md)\n- [Mapbox APIs + MCP vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapbox-vs-tomtom.md)\n- [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [MapTiler Cloud vs NextBillion.ai](https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md)\n- [MapTiler Cloud vs Nominatim](https://www.anchorterminal.com/compare/maptiler-vs-nominatim.md)\n- [MapTiler Cloud vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/maptiler-vs-opencage.md)\n- [MapTiler Cloud vs Radar](https://www.anchorterminal.com/compare/maptiler-vs-radar.md)\n- [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md)\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)\n- [Nominatim vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nominatim-vs-tomtom.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md)\n- [NextBillion.ai vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.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": "MapTiler Cloud vs TomTom Maps APIs + MCP", "url": "" } ], "description": "MapTiler Cloud scores 62.1 (B) to TomTom Maps's 45.9 (E) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MapTiler Cloud B 62.1", "TomTom Maps APIs + MCP E 45.9", "scores" ], "h1": "MapTiler Cloud vs TomTom Maps APIs + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/maptiler-vs-tomtom", "published": "2026-10-01", "section": "tools", "title": "MapTiler Cloud vs TomTom Maps for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/maptiler-vs-tomtom" }, "tokens": { "markdown": 4750, "slim": 2680 }, "version": 1 }