{ "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": "OpenCage Geocoding API scores 67.5 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "opencage", "name": "OpenCage Geocoding API", "vendor": "OpenCage", "vendorUrl": "https://opencagedata.com", "kind": "http-api", "category": "maps", "summary": "Forward and reverse geocoding on one endpoint, built on OpenStreetMap and other open data, with optional annotations and JSON, GeoJSON, XML or Google-compatible output.", "url": "https://www.anchorterminal.com/tools/opencage", "markdownUrl": "https://www.anchorterminal.com/tools/opencage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/opencage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/opencage.json", "dns": "opencage.grade.anchorterminal.com", "repo": "https://github.com/OpenCageData/opencage-geocoding-mcp", "license": "MIT (MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.opencagedata.com/geocode/v1/json", "packages": [ { "registry": "npm", "name": "@opencage/mcp-opencage-server" }, { "registry": "npm", "name": "opencage-api-client" }, { "registry": "pypi", "name": "opencage" } ], "auth": "api-key", "authNotes": "A 32-character key passed as the key query parameter. No headers are needed. The MCP server reads OPENCAGE_API_KEY.", "pricing": "paid", "pricingNotes": "Free trial of 2,500 requests a day at 1 a second, for testing only, no card. Monthly subscriptions by daily volume. X-Small $50 (10,000 a day, 15 a second), Small $125 (30,000 a day), Medium $500 (125,000 a day), Large $1,000 (300,000 a day), Enterprise from $2,000. Also priced in GBP (£40 to £800) and eleven other currencies. One-time plans are usable for up to a year. Subscriptions have no hard limits (https://opencagedata.com/pricing, https://opencagedata.com/api.md).", "priceSummary": "$50 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 19, "npmWeekly": 5501, "pypiWeekly": 137628, "asOf": "2026-09-30" }, "docsUrl": "https://opencagedata.com/api", "llmsTxt": "https://opencagedata.com/llms.txt", "registryName": "io.github.OpenCageData/opencage-geocoding-mcp", "capabilities": [ "geo.geocode", "geo.reverse" ], "tags": [ "hosted", "llms-txt", "mcp", "official", "python", "typescript", "open-data", "no-card", "eu" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 67.5, "grade": "B", "agentReady": false, "rank": 321, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 86, "payments": 35, "reliability": 85, "schema": 77, "security": 44, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "-3, one term for a breaking change marked in a minor release of the listing's own Python package with no advance notice found. opencage 3.5.0 (28 October 2026) raises network errors from requests and aiohttp as the new NetworkError and NetworkTimeoutError, and its changelog says 'Code catching requests.exceptions.* or aiohttp.ClientError must catch these instead'. The same release raised the minimum Python to 3.10, which isn't counted, as runtime-floor raises weren't for massive or vespa. https://github.com/OpenCageData/python-opencage-geocoder/blob/master/Changes.txt and https://pypi.org/project/opencage" ], "verdict": "OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.", "bestFor": "Bulk or repeated geocoding where results go into a database, and for EU data residency.", "strengths": [ "Permanent storage of results on every plan, including after you cancel", "Separate 402 (quota spent) and 429 (too fast) responses", "llms.txt with 70 or more Markdown pages, and agent skills on GitHub", "EU hosting, logs deleted after six months and a no_record option", "Subscriptions don't cut off or bill overage when you go over" ], "weaknesses": [ "Geocoding only, no place search or routing", "The key can only be sent as a query parameter", "Python SDK 3.5.0 (28 October 2026) replaced the network exceptions callers catch, in a minor release", "MCP server is stdio-only, has no tool annotations, and npm still serves 1.0.3 from September 2025", "No SOC 2 or ISO 27001 of its own, and the security bounty is on hold until December 2026" ], "agentNotes": [ "Add no_annotations=1 and limit=1 when you only need coordinates", "Stop on 402, which means the day's quota is gone, and back off on 429", "Add no_record=1 when the query holds personal data, and redact the key parameter before logging request URLs", "On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions", "Credit OpenStreetMap wherever you show results" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.5 } ], "editorialScores": { "ergonomics": 86, "maintenance": 86, "payments": 35, "reliability": 85, "schema": 77, "security": 44, "transparency": 84 }, "provenanceScore": 86, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.opencagedata.com/geocode/v1/json?q=10%20Downing%20Street%2C%20London\u0026limit=1\u0026no_annotations=1\u0026key=$OPENCAGE_API_KEY\"", "claudeCode": "claude mcp add opencage -e OPENCAGE_API_KEY=$OPENCAGE_API_KEY -- npx -y @opencage/mcp-opencage-server", "config": { "mcpServers": { "opencage": { "args": [ "-y", "@opencage/mcp-opencage-server" ], "command": "npx", "env": { "OPENCAGE_API_KEY": "${OPENCAGE_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/opencage" }, "area": "everyday", "unitPrices": [ { "item": "X-Small plan", "unit": "month", "usd": 50, "note": "10,000 requests a day, 15 a second" }, { "item": "Small plan", "unit": "month", "usd": 125, "note": "30,000 requests a day, 20 a second" }, { "item": "Medium plan", "unit": "month", "usd": 500, "note": "125,000 requests a day, 25 a second" }, { "item": "Large plan", "unit": "month", "usd": 1000, "note": "300,000 requests a day, 40 a second" } ], "provenance": { "legalEntity": "OpenCage GmbH", "domain": "opencagedata.com", "domainRegistered": "2013-05-16", "endpointOnVendorDomain": true, "terms": "https://opencagedata.com/terms", "privacy": "https://opencagedata.com/gdpr", "statusPage": "https://status.opencagedata.com", "changelog": "https://github.com/OpenCageData/opencagedata-misc-docs/blob/master/CHANGES.md", "securityTxt": "unknown", "checked": "2026-11-01", "notes": [ "The terms give a Berlin address, commercial register HRB 272249 and VAT ID DE323788688.", "Cancelling doesn't refund fees already paid. If OpenCage ends the service it refunds the rest of the billing period pro rata.", "robots.txt blocked our fetch of /.well-known/security.txt. A separate security policy page exists at opencagedata.com/security-policy.", "The API docs point to the dated changelog in OpenCageData/opencagedata-misc-docs (CHANGES.md). Changes are also announced on blog.opencagedata.com.", "The GDPR page was last updated 22 July 2026." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/opencage.json", "live": { "slug": "opencage", "probe": { "target": "https://api.opencagedata.com/geocode/v1/json", "method": "get", "lastAt": "2026-11-07T19:22:23.930680405Z", "lastOk": true, "lastStatus": 401, "lastMs": 145, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 197, "p95ms24h": 389, "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": 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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.opencagedata.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:31.928505068Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.OpenCageData/opencage-geocoding-mcp", "version": "1.0.3", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@opencage/mcp-opencage-server", "version": "1.0.3", "seenAt": "2026-11-06T23:52:21.882746366Z" }, { "registry": "npm", "name": "opencage-api-client", "version": "2.2.0", "seenAt": "2026-11-06T23:52:22.72317589Z" }, { "registry": "pypi", "name": "opencage", "version": "3.5.0", "released": "2026-10-28", "seenAt": "2026-11-06T23:52:24.090076618Z" } ], "githubStars": 19, "npmWeekly": 45, "pypiWeekly": 346657, "securityTxt": { "url": "https://opencagedata.com/.well-known/security.txt", "state": "valid", "expires": "2027-01-31T00:00:00z", "checkedAt": "2026-11-07T16:01:09.068391294Z" }, "llmsTxt": { "url": "https://opencagedata.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:30.784821868Z" }, "domain": { "domain": "opencagedata.com", "registered": "2013-05-16", "source": "https://rdap.verisign.com/com/v1/domain/opencagedata.com", "checkedAt": "2026-11-01T14:26:05.491227039Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/OpenCageData/opencagedata-misc-docs/master/CHANGES.md", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:19:03.194124022Z", "changedAt": "2026-11-05T13:03:27.937602667Z", "fingerprint": "e945174b90a2" }, { "url": "https://opencagedata.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:15:27.242684147Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2a4d55e4f714" }, { "url": "https://opencagedata.com/gdpr", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:15:25.157944889Z", "changedAt": "2026-10-07T18:07:57.615589937Z", "fingerprint": "a8a426817cc3" }, { "url": "https://opencagedata.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:15:29.307317397Z", "changedAt": "2026-10-07T18:08:01.691588303Z", "fingerprint": "30104a7082ce" } ], "github": { "repo": "opencagedata/opencage-geocoding-mcp", "checkedAt": "2026-11-02T09:13:16.433427419Z", "stars": 19, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T17:35:18Z", "openIssues": 0, "openPRs": 1, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 21, "ci": { "branch": "master", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-01T17:36:13Z" } }, "updatedAt": "2026-11-07T19:22:23.930680405Z" } }, "edges": [ { "by": 42, "category": "reliability", "leads": "opencage", "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": "Instatus page at status.opencagedata.com, measured by StatusCake, with forward geocoding, reverse geocoding, geosearch, the website and email sending as components (20). The incident history feed, read on 1 November 2026, lists nothing since the 26 June 2026 email outage, so the last 90 days are clean (30). Free trial limits of 2,500 a day and 1 a second, and per-second rates for each paid plan (15). 402 for a spent quota and 429 for going too fast are separate codes, and free and one-time plans get X-RateLimit-Limit, -Remaining and -Reset. There's no backoff guidance beyond '408 means try again' (10). No SLA found (0). GA (10)." }, "scores": { "a": 43, "b": 85 } }, { "by": 20, "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": "Plain revocable keys that can be disabled or tied to IP addresses, which earns 20 with 2 back for the IP rules. Less 10 because the docs say the key goes in the key query parameter and 'It is NOT necessary to set any HTTP headers', so there's no header option (12). The API only reads, so there's nothing to approve (15). Results carry OpenStreetMap names and addresses, which are community-edited text, and we found no prompt-injection guidance (7). The MCP's get-opencage-info tool reports usage and rate state. We didn't check the dashboard's per-call visibility (3). A security policy page, a security@opencagedata.com contact and a SECURITY.md on GitHub. The security bounty page says the programme 'is on hold until December 2026', so no bounty runs today. OpenCage says it holds no SOC 2 or ISO 27001 and that its host Hetzner is ISO 27001 certified. security.txt couldn't be checked because robots.txt blocks it. That is below contactsplus (8, discretionary bounties running) (7)." }, "scores": { "a": 64, "b": 44 } }, { "by": 16, "category": "ergonomics", "leads": "opencage", "name": "Agent ergonomics", "reasons": { "a": "API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.", "b": "Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15)." }, "scores": { "a": 70, "b": 86 } }, { "by": 16, "category": "maintenance", "leads": "opencage", "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": "The newest API changelog entry is 15 October 2026 (SMDG port terminal codes), and the Python SDK released 3.5.0 on 28 October 2026, both within 30 days (30). Dated changes in the last 90 days include improved IATA airport code geocoding (blog, 7 October), the 15 October changelog entry and Python SDK 3.5.0, with spreadsheet upload improvements on 14 August (20). Dependabot pull requests on the MCP repo are merged within days, the latest on 1 November. We couldn't see issue reply times from git (15). In the official MCP registry as io.github.OpenCageData/opencage-geocoding-mcp, and the Python SDK is current at 3.5.0 (15). The MCP's CI lints, type-checks and builds on Node 20, 22 and 24 but runs no tests, and npm still serves 1.0.3 from 11 September 2025 while the repo is at 1.0.5 (6)." }, "scores": { "a": 70, "b": 86 } }, { "by": 5, "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). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0)." }, "scores": { "a": 40, "b": 35 } }, { "by": 5, "category": "transparency", "leads": "opencage", "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 service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20)." }, "scores": { "a": 80, "b": 85 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MapTiler AG", "b": "OpenCage", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.opencagedata.com/geocode/v1/json", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "MIT (MCP server)", "name": "Licence" }, { "a": "none", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.OpenCageData/opencage-geocoding-mcp", "name": "MCP registry" }, { "a": "2026-10-02", "b": "2026-10-28", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "115k npm/wk", "b": "19 stars, 5.5k npm/wk, 138k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "OpenCage Geocoding API scores 67.5 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, MapTiler Cloud or OpenCage Geocoding API?" }, { "answer": "Both need an API key.", "question": "Do MapTiler Cloud and OpenCage Geocoding API need an API key?" }, { "answer": "No hosted endpoint is listed for MapTiler Cloud. OpenCage Geocoding API has a hosted endpoint at https://api.opencagedata.com/geocode/v1/json.", "question": "Can an agent call MapTiler Cloud and OpenCage Geocoding API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 64 against 44", "Payments \u0026 pricing, 40 against 35" ], "also": [ "No incidents deducted, where OpenCage Geocoding API loses 3 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": [ "Reliability, 85 against 43", "Agent ergonomics, 86 against 70", "Maintenance \u0026 community, 86 against 70", "Transparency \u0026 trust, 85 against 80" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Bulk or repeated geocoding where results go into a database, and for EU data residency.", "slug": "opencage", "watchFor": "Geocoding only, no place search or routing" } ], "history": { "maptiler": null, "opencage": [ { "causes": [ "security", "product", "event" ], "date": "2026-11-01", "delta": -1.8, "from": 69.3, "fromGrade": "B", "to": 67.5, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 69.2, "fromGrade": "B", "to": 69.3, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 69.5, "fromGrade": "B", "to": 69.2, "toGrade": "B" } ] }, "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-opencage.json", "title": "Amazon Location Service vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-opencage" }, { "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-opencage.json", "title": "ArcGIS Location Platform vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/arcgis-vs-opencage" }, { "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-opencage.json", "title": "Azure Maps vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-opencage" }, { "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-opencage.json", "title": "Geoapify Location Platform + MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geoapify-vs-opencage" }, { "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-opencage.json", "title": "Geocodio vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geocodio-vs-opencage" }, { "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-opencage.json", "title": "Google Maps Platform + Grounding Lite MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-opencage" }, { "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-opencage.json", "title": "HERE Location Services vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/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-opencage.json", "title": "LocationIQ vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/locationiq-vs-opencage" }, { "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-opencage.json", "title": "Mapbox APIs + MCP vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapbox-vs-opencage" }, { "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-opencage.json", "title": "MapQuest vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapquest-vs-opencage" }, { "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-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-tomtom.json", "title": "MapTiler Cloud vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/maptiler-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/nextbillion-vs-opencage.json", "title": "NextBillion.ai vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/nextbillion-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/nominatim-vs-opencage.json", "title": "Nominatim vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/nominatim-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-radar.json", "title": "OpenCage Geocoding API vs Radar", "url": "https://www.anchorterminal.com/compare/opencage-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.json", "title": "OpenCage Geocoding API vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/opencage-vs-stadia-maps" }, { "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/opencage-vs-woosmap.json", "title": "OpenCage Geocoding API vs Woosmap", "url": "https://www.anchorterminal.com/compare/opencage-vs-woosmap" } ], "panel": null, "scores": [ { "by": 42, "edge": "opencage", "key": "reliability", "maptiler": 43, "name": "Reliability", "opencage": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "maptiler", "key": "schema", "maptiler": 79, "name": "Schema \u0026 documentation", "opencage": 77, "weight": 13 }, { "by": 16, "edge": "opencage", "key": "ergonomics", "maptiler": 70, "name": "Agent ergonomics", "opencage": 86, "weight": 13 }, { "by": 20, "edge": "maptiler", "key": "security", "maptiler": 64, "name": "Security \u0026 auth", "opencage": 44, "weight": 14 }, { "by": 5, "edge": "maptiler", "key": "payments", "maptiler": 40, "name": "Payments \u0026 pricing", "opencage": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "opencage", "key": "maintenance", "maptiler": 70, "name": "Maintenance \u0026 community", "opencage": 86, "weight": 7 }, { "by": 5, "edge": "opencage", "key": "transparency", "maptiler": 80, "name": "Transparency \u0026 trust", "opencage": 85, "weight": 7 } ], "summary": "OpenCage Geocoding API scores 67.5 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on security \u0026 auth and payments \u0026 pricing. 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.", "opencage": "OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/maptiler-vs-opencage", "json": "https://www.anchorterminal.com/compare/maptiler-vs-opencage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/maptiler-vs-opencage.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/maptiler-vs-opencage.min.md" }, "markdown": "OpenCage Geocoding API scores 67.5 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on security \u0026 auth and payments \u0026 pricing. 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- OpenCage Geocoding API: grade B, 67.5/100, rank #321 of 1510. Markdown https://www.anchorterminal.com/tools/opencage.md · JSON https://www.anchorterminal.com/api/v1/tools/opencage.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- Security \u0026 auth, 64 against 44\n- Payments \u0026 pricing, 40 against 35\n\nAlso in its favour:\n- No incidents deducted, where OpenCage Geocoding API loses 3 points for them\n\nWatch for: The API key is always sent as a query parameter\n\n### OpenCage Geocoding API (B)\n\nGood for: Bulk or repeated geocoding where results go into a database, and for EU data residency.\n\nAhead on:\n- Reliability, 85 against 43\n- Agent ergonomics, 86 against 70\n- Maintenance \u0026 community, 86 against 70\n- Transparency \u0026 trust, 85 against 80\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Geocoding only, no place search or routing\n\n\n## Why the edge\n\n### Reliability: OpenCage Geocoding API +42\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- OpenCage Geocoding API (85): Instatus page at status.opencagedata.com, measured by StatusCake, with forward geocoding, reverse geocoding, geosearch, the website and email sending as components (20). The incident history feed, read on 1 November 2026, lists nothing since the 26 June 2026 email outage, so the last 90 days are clean (30). Free trial limits of 2,500 a day and 1 a second, and per-second rates for each paid plan (15). 402 for a spent quota and 429 for going too fast are separate codes, and free and one-time plans get X-RateLimit-Limit, -Remaining and -Reset. There's no backoff guidance beyond '408 means try again' (10). No SLA found (0). GA (10).\n\n### Security \u0026 auth: MapTiler Cloud +20\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- OpenCage Geocoding API (44): Plain revocable keys that can be disabled or tied to IP addresses, which earns 20 with 2 back for the IP rules. Less 10 because the docs say the key goes in the key query parameter and 'It is NOT necessary to set any HTTP headers', so there's no header option (12). The API only reads, so there's nothing to approve (15). Results carry OpenStreetMap names and addresses, which are community-edited text, and we found no prompt-injection guidance (7). The MCP's get-opencage-info tool reports usage and rate state. We didn't check the dashboard's per-call visibility (3). A security policy page, a security@opencagedata.com contact and a SECURITY.md on GitHub. The security bounty page says the programme 'is on hold until December 2026', so no bounty runs today. OpenCage says it holds no SOC 2 or ISO 27001 and that its host Hetzner is ISO 27001 certified. security.txt couldn't be checked because robots.txt blocks it. That is below contactsplus (8, discretionary bounties running) (7).\n\n### Agent ergonomics: OpenCage Geocoding API +16\n\n- MapTiler Cloud (70): API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.\n- OpenCage Geocoding API (86): Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15).\n\n### Maintenance \u0026 community: OpenCage Geocoding API +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- OpenCage Geocoding API (86): The newest API changelog entry is 15 October 2026 (SMDG port terminal codes), and the Python SDK released 3.5.0 on 28 October 2026, both within 30 days (30). Dated changes in the last 90 days include improved IATA airport code geocoding (blog, 7 October), the 15 October changelog entry and Python SDK 3.5.0, with spreadsheet upload improvements on 14 August (20). Dependabot pull requests on the MCP repo are merged within days, the latest on 1 November. We couldn't see issue reply times from git (15). In the official MCP registry as io.github.OpenCageData/opencage-geocoding-mcp, and the Python SDK is current at 3.5.0 (15). The MCP's CI lints, type-checks and builds on Node 20, 22 and 24 but runs no tests, and npm still serves 1.0.3 from 11 September 2025 while the repo is at 1.0.5 (6).\n\n### Payments \u0026 pricing: MapTiler Cloud +5\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- OpenCage Geocoding API (35): No x402, MPP or L402 (0). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0).\n\n### Transparency \u0026 trust: OpenCage Geocoding API +5\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- OpenCage Geocoding API (85): Closed service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20).\n\n## Score by category\n\n| Category | Weight | MapTiler Cloud | OpenCage Geocoding API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 43 | 85 | OpenCage Geocoding API +42 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 77 | MapTiler Cloud +2 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 86 | OpenCage Geocoding API +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 44 | MapTiler Cloud +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | MapTiler Cloud +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 86 | OpenCage Geocoding API +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 85 | OpenCage Geocoding API +5 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **62.1 · B** | **67.5 · B** | |\n\n## Facts side by side\n\n| Fact | MapTiler Cloud | OpenCage Geocoding API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MapTiler AG | OpenCage |\n| Hosted endpoint | no (local only) | `https://api.opencagedata.com/geocode/v1/json` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | none | MIT (MCP server) |\n| Tools exposed | none | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.OpenCageData/opencage-geocoding-mcp` |\n| Last release | 2026-10-02 | 2026-10-28 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 115k npm/wk | 19 stars, 5.5k npm/wk, 138k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### MapTiler Cloud\n\nNo score change since it was listed.\n\n### OpenCage Geocoding API\n\n- -1.8 on 1 November 2026: security, product, negative event\n- +0.1 on 27 October 2026: checklist\n- -0.3 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**OpenCage Geocoding API.** OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.\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### OpenCage Geocoding API\n\n1. Add no_annotations=1 and limit=1 when you only need coordinates\n2. Stop on 402, which means the day's quota is gone, and back off on 429\n3. Add no_record=1 when the query holds personal data, and redact the key parameter before logging request URLs\n4. On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions\n5. Credit OpenStreetMap wherever you show results\n\n## Questions\n\n### Which is better for AI agents, MapTiler Cloud or OpenCage Geocoding API?\n\nOpenCage Geocoding API scores 67.5 (B) on agent readiness against MapTiler Cloud's 62.1 (B), and leads in 4 of 7 scored categories. MapTiler Cloud leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do MapTiler Cloud and OpenCage Geocoding API need an API key?\n\nBoth need an API key.\n\n### Can an agent call MapTiler Cloud and OpenCage Geocoding API without installing anything?\n\nNo hosted endpoint is listed for MapTiler Cloud. OpenCage Geocoding API has a hosted endpoint at https://api.opencagedata.com/geocode/v1/json.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/maptiler-vs-opencage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/maptiler-vs-opencage.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"maptiler\", \"b\": \"opencage\"}`. From a terminal: `anchor compare maptiler opencage`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/maptiler.json and https://www.anchorterminal.com/api/v1/tools/opencage.json\n\n## Other comparisons with MapTiler Cloud or OpenCage Geocoding API\n\n- [Amazon Location Service vs MapTiler Cloud](https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.md)\n- [Amazon Location Service vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/amazon-location-vs-opencage.md)\n- [ArcGIS Location Platform vs MapTiler Cloud](https://www.anchorterminal.com/compare/arcgis-vs-maptiler.md)\n- [ArcGIS Location Platform vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/arcgis-vs-opencage.md)\n- [Azure Maps vs MapTiler Cloud](https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.md)\n- [Azure Maps vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/azure-maps-vs-opencage.md)\n- [Geoapify Location Platform + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/geoapify-vs-maptiler.md)\n- [Geoapify Location Platform + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geoapify-vs-opencage.md)\n- [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md)\n- [Geocodio vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geocodio-vs-opencage.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 OpenCage Geocoding API](https://www.anchorterminal.com/compare/google-maps-platform-vs-opencage.md)\n- [HERE Location Services vs MapTiler Cloud](https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [LocationIQ vs MapTiler Cloud](https://www.anchorterminal.com/compare/locationiq-vs-maptiler.md)\n- [LocationIQ vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/locationiq-vs-opencage.md)\n- [Mapbox APIs + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapbox-vs-maptiler.md)\n- [Mapbox APIs + MCP vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapbox-vs-opencage.md)\n- [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md)\n- [MapQuest vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapquest-vs-opencage.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 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 TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/maptiler-vs-tomtom.md)\n- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)\n- [NextBillion.ai vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/nextbillion-vs-opencage.md)\n- [Nominatim vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/nominatim-vs-opencage.md)\n- [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/opencage-vs-tomtom.md)\n- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-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": "MapTiler Cloud vs OpenCage Geocoding API", "url": "" } ], "description": "OpenCage Geocoding scores 67.5 (B) to MapTiler Cloud's 62.1 (B) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MapTiler Cloud B 62.1", "OpenCage Geocoding API B 67.5", "scores" ], "h1": "MapTiler Cloud vs OpenCage Geocoding API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/maptiler-vs-opencage", "published": "2026-10-01", "section": "tools", "title": "MapTiler Cloud vs OpenCage Geocoding for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/maptiler-vs-opencage" }, "tokens": { "markdown": 4750, "slim": 2580 }, "version": 1 }