{
  "data": {
    "a": {
      "slug": "here-location-services",
      "name": "HERE Location Services",
      "vendor": "HERE Technologies",
      "vendorUrl": "https://www.here.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "HERE Technologies' REST APIs for geocoding, place search, routing, matrix and isoline routing, traffic, transit and map tiles, called with an API key or OAuth token. A hosted MCP server, HERE Location Reasoning, exposes 13 of these operations as tools.",
      "url": "https://www.anchorterminal.com/tools/here-location-services",
      "markdownUrl": "https://www.anchorterminal.com/tools/here-location-services.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/here-location-services.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/here-location-services.json",
      "license": "Proprietary service under the HERE Platform Terms",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://geocode.search.hereapi.com/v1",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Self-serve. A HERE platform account, created in a browser with email verification, lets a person register an app and create up to two API keys, OAuth 2.0 credentials or OAuth 2.1 `private_key_jwt` credentials. REST calls take the key as the `apiKey` query parameter or a bearer token from https://account.api.here.com/oauth2/token. Location Reasoning needs a bearer token on `tools/call` and an account entitlement, and returns 403 without one.",
      "pricing": "freemium",
      "pricingNotes": "HERE's docs say a new organisation can get started for free on the Base Plan. The price table at here.com/get-started/pricing is drawn by script and was not read, so no allowance or per-request price is quoted. Support plans run from $50 a month (Developer). Location Reasoning is also sold through AWS Marketplace (checked 2026-10-09).",
      "priceSummary": "Freemium",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the Location Reasoning guides or the Platform Terms (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": 13,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.here.com",
      "llmsTxt": "https://docs.here.com/llms.txt",
      "openapi": "https://docs.here.com/geocoding-and-search/reference/get_geocode.md",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "mcp",
        "official",
        "openapi",
        "llms-txt",
        "oauth",
        "free-tier",
        "enterprise",
        "eu",
        "sla",
        "closed-source"
      ],
      "lastRelease": "2026-09-09",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 58,
        "grade": "C",
        "agentReady": false,
        "rank": 591,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 9,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 60,
          "payments": 10,
          "reliability": 57,
          "schema": 87,
          "security": 65,
          "transparency": 63
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -3,
        "negativeNotes": [
          "10 July 2026. The Routing v8 changelog marks `mlDuration` as Deprecated and says `return=mlDuration` is still accepted but no longer returns a value. HERE's lifecycle policy says a deprecated feature continues to operate for 6 to 12 months after notice. Three points (https://docs.here.com/routing/docs/routing-v8-changelog.md)"
        ],
        "verdict": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.",
        "bestFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.",
        "strengths": [
          "Every endpoint page has a Markdown twin holding its OpenAPI 3.0 definition, indexed from `llms.txt` files per product",
          "99.9 per cent monthly availability targets published for Geocoding and Search v7 and Routing v8",
          "Lifecycle policy promises six months' notice before a product is discontinued and 6 to 12 months for a deprecated feature",
          "OAuth 2.1 `private_key_jwt` credentials alongside API keys, with two keys an app for rotation and trusted-domain limits",
          "ISO 27001, 27701, 27017, 27018 and 42001 certificates, TISAX AL3, and SOC 2 Type 2 for Platform Foundation and Workspace"
        ],
        "weaknesses": [
          "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run",
          "The Base Plan price table is drawn by script, so per-request prices, free allowances and rate limits were not read",
          "API keys travel in the `apiKey` query parameter",
          "Results may be cached or stored outside the platform for 30 days at most, and only as HTTP caching headers allow",
          "Location Reasoning returns 403 unless the account is entitled, and the docs send the reader to an account representative or AWS Marketplace",
          "The acceptable use policy of January 2022 lists benchmarking and scraping among prohibited activities"
        ],
        "agentNotes": [
          "Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL",
          "Do not store results for more than 30 days, and follow the HTTP caching headers on each response",
          "Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota",
          "Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support",
          "For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 58
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 60,
          "payments": 10,
          "reliability": 57,
          "schema": 87,
          "security": 65,
          "transparency": 52
        },
        "provenanceScore": 73
      },
      "connect": {
        "http": "curl \"https://geocode.search.hereapi.com/v1/geocode?q=240+Washington+St.%2C+Boston\u0026limit=4\u0026apiKey=$HERE_API_KEY\""
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/here-location-services"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "HERE Europe B.V.",
        "domain": "here.com",
        "domainRegistered": "1995-06-11",
        "endpointOnVendorDomain": false,
        "terms": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023",
        "privacy": "https://www.here.com/en-gb/privacy",
        "statusPage": "https://status.here.com/status",
        "changelog": "https://docs.here.com/routing/docs/routing-v8-changelog",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The HERE Platform Terms, effective 18 September 2023, name HERE Europe B.V., Kennedyplein 222-226, 5611 ZT Eindhoven, as contracting party, and HERE North America, LLC, Chicago, for customers in the Americas.",
          "The privacy policy, effective 29 August 2024, names HERE Global B.V. as controller and says it does not apply to personal data processed on behalf of customers. The Platform Terms incorporate it and a Data Processing Agreement published as a PDF.",
          "The APIs answer on hereapi.com (for example geocode.search.hereapi.com and router.hereapi.com) and the MCP server on hlr.here.ai, both second domains of the vendor.",
          "www.here.com/.well-known/security.txt returned the site's error page. The security page gives security@here.com and a 90-day disclosure window.",
          "RDAP for here.com gives a registration date of 1995-06-11.",
          "legal.here.com/en-gb/terms/here-platform redirects to the September 2023 terms on www.here.com."
        ],
        "score": 73
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/here-location-services.json",
      "live": {
        "slug": "here-location-services",
        "probe": {
          "target": "https://geocode.search.hereapi.com/v1",
          "method": "get",
          "lastAt": "2026-10-10T02:54:57.537414358Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 60,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 55,
          "p95ms24h": 124,
          "samples24h": 115,
          "samples30d": 115,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.here.com/status",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:50:40.516930569Z"
        },
        "pages": [
          {
            "url": "https://docs.here.com/routing/docs/routing-v8-changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:37:28.07952108Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "c940c6209b7e"
          },
          {
            "url": "https://www.here.com/en-gb/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:50:53.049981302Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "bbe0eed0a23e"
          },
          {
            "url": "https://www.here.com/en-gb/terms/here-platform-terms-september-2023",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:50:55.117836401Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "466d77d5e000"
          }
        ],
        "updatedAt": "2026-10-10T02:54:57.537414358Z"
      }
    },
    "answer": "Stadia Maps scores 65.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on security \u0026 auth.",
    "b": {
      "slug": "stadia-maps",
      "name": "Stadia Maps",
      "vendor": "Stadia Maps",
      "vendorUrl": "https://stadiamaps.com",
      "kind": "http-api",
      "category": "maps",
      "summary": "Geocoding, reverse geocoding, autocomplete and place details, routing, matrix, isochrones, static maps and hosted vector, raster and satellite tiles, sold in credits on plans from $20 a month.",
      "url": "https://www.anchorterminal.com/tools/stadia-maps",
      "markdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stadia-maps.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stadia-maps.json",
      "repo": "https://github.com/stadiamaps/stadiamaps-mcp-server-ts",
      "license": "BSD-3-Clause (MCP server)",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://api.stadiamaps.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@stadiamaps/api"
        },
        {
          "registry": "pypi",
          "name": "stadiamaps"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key as the api_key query parameter or in an `Authorization: Stadia-Auth \u003ckey\u003e` header. Browser apps can use domain-based auth with no key, checked against the Origin and Referer headers. The MCP server reads API_KEY.",
      "pricing": "freemium",
      "pricingNotes": "Free 200,000 credits a month for development, testing and demos only, no commercial use. Starter $20 a month (1 million credits), Standard $80 (7.5 million), Professional $250 (25 million), with overage at $0.03, $0.02 and $0.015 per 1,000 credits. A forward, reverse or structured geocode, a place lookup, an Autocomplete v1 search or a route is 20 credits, Autocomplete v2 is 1, a matrix element 10, a map tile 1 and a satellite tile 4, so Starter covers 50,000 geocodes. New accounts get a 14-day Professional trial with no card (https://stadiamaps.com/pricing/). When credits run out you get 429 until the next cycle unless pay-as-you-go is on (https://stadiamaps.com/faqs/).",
      "priceSummary": "$20 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": 6,
      "popularity": {
        "githubStars": 23,
        "npmWeekly": 6058,
        "pypiWeekly": 192,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.stadiamaps.com",
      "llmsTxt": "https://docs.stadiamaps.com/llms.txt",
      "openapi": "https://api.stadiamaps.com/openapi.yaml",
      "capabilities": [
        "geo.geocode",
        "geo.reverse",
        "geo.places",
        "geo.routing",
        "geo.tiles"
      ],
      "tags": [
        "hosted",
        "mcp",
        "llms-txt",
        "official",
        "typescript",
        "python",
        "free-tier",
        "no-card",
        "open-data"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 65.2,
        "grade": "B",
        "agentReady": false,
        "rank": 325,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 80,
          "maintenance": 80,
          "payments": 40,
          "reliability": 63,
          "schema": 86,
          "security": 40,
          "transparency": 76
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.",
        "bestFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.",
        "strengths": [
          "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs",
          "Published credit costs, with 50,000 geocodes for $20 a month on Starter",
          "Header auth keeps the key out of URLs, and keys rotate through an API",
          "Server logs kept about 7 to 14 days, and a DPA",
          "14 dated changelog entries between June and September 2026"
        ],
        "weaknesses": [
          "Free plan is for development, testing and demos only",
          "The same 429 signals a burst or a spent month of credits, with no Retry-After",
          "No SLA, no security.txt and no disclosure policy found",
          "MCP server has no release, no CI and no commits since 29 July 2025",
          "The terms forbid benchmarking against competitors without written permission"
        ],
        "agentNotes": [
          "Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL",
          "Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough",
          "Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent",
          "Don't write geocodes to a database on Free or Starter",
          "Use bulk-geocode for addresses only, not POI names"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 65.2
          }
        ],
        "editorialScores": {
          "ergonomics": 80,
          "maintenance": 80,
          "payments": 40,
          "reliability": 63,
          "schema": 86,
          "security": 40,
          "transparency": 72
        },
        "provenanceScore": 79
      },
      "connect": {
        "http": "curl -H \"Authorization: Stadia-Auth $STADIA_API_KEY\" \"https://api.stadiamaps.com/geocoding/v1/search?text=10%20Downing%20Street%2C%20London\u0026size=1\""
      },
      "letme": {
        "capability": "https://letme.dev/geo.geocode",
        "tool": "https://letme.dev/stadia-maps"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Starter plan",
          "unit": "month",
          "usd": 20,
          "note": "1 million credits, about 50,000 geocodes"
        },
        {
          "item": "Standard plan",
          "unit": "month",
          "usd": 80,
          "note": "7.5 million credits, permanent geocode storage"
        },
        {
          "item": "Professional plan",
          "unit": "month",
          "usd": 250,
          "note": "25 million credits"
        },
        {
          "item": "Geocoding within Starter",
          "unit": "1k-requests",
          "usd": 0.4,
          "note": "20 credits each, $20 for 1 million credits"
        },
        {
          "item": "Geocoding overage on Starter",
          "unit": "1k-requests",
          "usd": 0.6,
          "note": "20 credits each at $0.03 per 1,000 credits"
        }
      ],
      "provenance": {
        "legalEntity": "Stadia Maps, Inc.",
        "domain": "stadiamaps.com",
        "domainRegistered": "2016-11-30",
        "endpointOnVendorDomain": true,
        "terms": "https://stadiamaps.com/terms-of-service/",
        "privacy": "https://stadiamaps.com/privacy/privacy-policy/",
        "statusPage": "https://status.stadiamaps.com",
        "changelog": "https://stadiamaps.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "The terms name Stadia Maps, Inc., a Delaware corporation with an address in East Lansing, Michigan, under Delaware law. Last updated 18 March 2026.",
          "Pages showing Traffic Products must carry \"© Stadia Maps © TomTom\".",
          "stadiamaps.com/.well-known/security.txt returns 404."
        ],
        "score": 79
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/stadia-maps.json",
      "live": {
        "slug": "stadia-maps",
        "probe": {
          "target": "https://api.stadiamaps.com",
          "method": "get",
          "lastAt": "2026-10-10T02:55:11.727830498Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 35,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 42,
          "p95ms24h": 95,
          "samples24h": 249,
          "samples30d": 2264,
          "days": [
            {
              "date": "2026-10-01",
              "probes": 109,
              "ok": 109
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "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": 30,
              "ok": 30
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.stadiamaps.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-10T00:51:17.490240835Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@stadiamaps/api",
            "version": "9.1.0",
            "seenAt": "2026-10-09T17:21:50.345880733Z"
          },
          {
            "registry": "pypi",
            "name": "stadiamaps",
            "version": "8.1.0",
            "released": "2026-04-27",
            "seenAt": "2026-10-09T17:21:51.5013462Z"
          }
        ],
        "githubStars": 23,
        "npmWeekly": 6095,
        "pypiWeekly": 312,
        "securityTxt": {
          "url": "https://stadiamaps.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:40:12.562122058Z"
        },
        "llmsTxt": {
          "url": "https://docs.stadiamaps.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:50.327374015Z"
        },
        "domain": {
          "domain": "stadiamaps.com",
          "registered": "2016-11-30",
          "source": "https://rdap.verisign.com/com/v1/domain/stadiamaps.com",
          "checkedAt": "2026-10-04T13:06:24.947269949Z"
        },
        "pages": [
          {
            "url": "https://stadiamaps.com/changelog/",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-10-09T18:45:52.564812251Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "fb379c6fd6fb"
          },
          {
            "url": "https://stadiamaps.com/pricing/",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-10-09T18:45:54.652518062Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "aeba9483f45f"
          },
          {
            "url": "https://stadiamaps.com/privacy/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:45:56.582260444Z",
            "changedAt": "2026-10-09T18:45:56.582260444Z",
            "fingerprint": "24369fa2e373"
          },
          {
            "url": "https://stadiamaps.com/terms-of-service/",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-10-09T18:45:58.692681695Z",
            "changedAt": "2026-10-08T18:24:51.381996532Z",
            "fingerprint": "44e2e273da24"
          }
        ],
        "updatedAt": "2026-10-10T02:55:11.727830498Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "HERE Technologies",
        "b": "Stadia Maps",
        "name": "Vendor"
      },
      {
        "a": "https://geocode.search.hereapi.com/v1",
        "b": "https://api.stadiamaps.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "not published",
        "b": "$0.40 per 1,000 requests",
        "name": "Price for geocoding"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the HERE Platform Terms",
        "b": "BSD-3-Clause (MCP server)",
        "name": "Licence"
      },
      {
        "a": "13",
        "b": "6",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-09",
        "b": "2026-09-30",
        "name": "Last release"
      },
      {
        "a": "2023-09-18",
        "b": "2026-03-18",
        "name": "Terms last updated"
      },
      {
        "a": "2024-08-29",
        "b": "2026-10-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "23 stars, 6.1k npm/wk, 192 PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Stadia Maps scores 65.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on security \u0026 auth.",
        "question": "Which is better for AI agents, HERE Location Services or Stadia Maps?"
      },
      {
        "answer": "HERE Location Services takes an API key or an OAuth sign-in. Stadia Maps needs an API key.",
        "question": "Do HERE Location Services and Stadia Maps need an API key?"
      },
      {
        "answer": "Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Stadia Maps at https://api.stadiamaps.com.",
        "question": "Can an agent call HERE Location Services and Stadia Maps without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 65 against 40"
        ],
        "also": null,
        "goodFor": "Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.",
        "slug": "here-location-services",
        "watchFor": "Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run"
      },
      {
        "aheadOn": [
          "Reliability, 63 against 57",
          "Agent ergonomics, 80 against 74",
          "Payments \u0026 pricing, 40 against 10",
          "Maintenance \u0026 community, 80 against 60",
          "Transparency \u0026 trust, 76 against 63"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card",
          "No incidents deducted, where HERE Location Services loses 3 points for them"
        ],
        "goodFor": "Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.",
        "slug": "stadia-maps",
        "watchFor": "Free plan is for development, testing and demos only"
      }
    ],
    "job": {
      "capability": "geo.geocode",
      "name": "Geocoding"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.json",
        "title": "Amazon Location Service vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.json",
        "title": "Amazon Location Service vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.json",
        "title": "ArcGIS Location Platform vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/arcgis-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.json",
        "title": "ArcGIS Location Platform vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.json",
        "title": "Azure Maps vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.json",
        "title": "Azure Maps vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.json",
        "title": "Geoapify Location Platform + MCP vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.json",
        "title": "Geoapify Location Platform + MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs HERE Location Services",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.json",
        "title": "Google Maps Platform + Grounding Lite MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.json",
        "title": "HERE Location Services vs LocationIQ",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-locationiq"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.json",
        "title": "HERE Location Services vs Mapbox APIs + MCP",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json",
        "title": "HERE Location Services vs MapQuest",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage.json",
        "title": "HERE Location Services vs OpenCage Geocoding API",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-opencage"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-radar.json",
        "title": "HERE Location Services vs Radar",
        "url": "https://www.anchorterminal.com/compare/here-location-services-vs-radar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/here-location-services-vs-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-stadia-maps.json",
        "title": "LocationIQ vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.json",
        "title": "Mapbox APIs + MCP vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json",
        "title": "MapQuest vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/radar-vs-stadia-maps.json",
        "title": "Radar vs Stadia Maps",
        "url": "https://www.anchorterminal.com/compare/radar-vs-stadia-maps"
      },
      {
        "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"
      }
    ],
    "scores": [
      {
        "by": 6,
        "edge": "stadia-maps",
        "here-location-services": 57,
        "key": "reliability",
        "name": "Reliability",
        "stadia-maps": 63,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "here-location-services",
        "here-location-services": 87,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "stadia-maps": 86,
        "weight": 13
      },
      {
        "by": 6,
        "edge": "stadia-maps",
        "here-location-services": 74,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "stadia-maps": 80,
        "weight": 13
      },
      {
        "by": 25,
        "edge": "here-location-services",
        "here-location-services": 65,
        "key": "security",
        "name": "Security \u0026 auth",
        "stadia-maps": 40,
        "weight": 14
      },
      {
        "by": 30,
        "edge": "stadia-maps",
        "here-location-services": 10,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "stadia-maps": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 20,
        "edge": "stadia-maps",
        "here-location-services": 60,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "stadia-maps": 80,
        "weight": 7
      },
      {
        "by": 13,
        "edge": "stadia-maps",
        "here-location-services": 63,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "stadia-maps": 76,
        "weight": 7
      }
    ],
    "summary": "Stadia Maps scores 65.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on security \u0026 auth. Both do geocoding.",
    "verdicts": {
      "here-location-services": "Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.",
      "stadia-maps": "Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps",
    "json": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.md",
    "slim": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.min.md"
  },
  "markdown": "Stadia Maps scores 65.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on security \u0026 auth. Both do geocoding.\n\n- HERE Location Services: grade C, 58/100, rank #591 of 950. Markdown https://www.anchorterminal.com/tools/here-location-services.md · JSON https://www.anchorterminal.com/api/v1/tools/here-location-services.json\n- Stadia Maps: grade B, 65.2/100, rank #325 of 950. Markdown https://www.anchorterminal.com/tools/stadia-maps.md · JSON https://www.anchorterminal.com/api/v1/tools/stadia-maps.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### HERE Location Services (C)\n\nGood for: Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.\n\nAhead on:\n- Security \u0026 auth, 65 against 40\n\nWatch for: Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run\n\n### Stadia Maps (B)\n\nGood for: Cost-sensitive geocoding, routing and tiles on OpenStreetMap data, with traffic-influenced routing since April 2026.\n\nAhead on:\n- Reliability, 63 against 57\n- Agent ergonomics, 80 against 74\n- Payments \u0026 pricing, 40 against 10\n- Maintenance \u0026 community, 80 against 60\n- Transparency \u0026 trust, 76 against 63\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n- No incidents deducted, where HERE Location Services loses 3 points for them\n\nWatch for: Free plan is for development, testing and demos only\n\n\n## Score by category\n\n| Category | Weight | HERE Location Services | Stadia Maps | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 63 | Stadia Maps +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 86 | HERE Location Services +1 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 80 | Stadia Maps +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 40 | HERE Location Services +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 40 | Stadia Maps +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 80 | Stadia Maps +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 76 | Stadia Maps +13 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **58 · C** | **65.2 · B** | |\n\n## Facts side by side\n\n| Fact | HERE Location Services | Stadia Maps |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HERE Technologies | Stadia Maps |\n| Hosted endpoint | `https://geocode.search.hereapi.com/v1` | `https://api.stadiamaps.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| Price for geocoding | not published | $0.40 per 1,000 requests |\n| x402 | no | no |\n| Licence | Proprietary service under the HERE Platform Terms | BSD-3-Clause (MCP server) |\n| Tools exposed | 13 | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-09 | 2026-09-30 |\n| Terms last updated | 2023-09-18 | 2026-03-18 |\n| Privacy policy last updated | 2024-08-29 | 2026-10-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 23 stars, 6.1k npm/wk, 192 PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\n\n**HERE Location Services.** Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.\n\n**Stadia Maps.** Public OpenAPI spec (11.1.0) with generated TypeScript and Python SDKs. Free plan is for development, testing and demos only.\n\n## Before you call either\n\n### HERE Location Services\n\n1. Send `Authorization: Bearer` with an OAuth token where logs are kept. The `apiKey` query parameter puts the secret in every URL\n2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response\n3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota\n4. Read `code`, `cause` and `action` in the error body, and quote `correlationId` to support\n5. For Location Reasoning, send `initialize`, keep the `Mcp-Session-Id` header on later calls, and send a bearer token on `tools/call`\n\n### Stadia Maps\n\n1. Send the key as `Authorization: Stadia-Auth \u003ckey\u003e` rather than in the URL\n2. Try Autocomplete v2 (1 credit) before a full geocode (20 credits) when a name is enough\n3. Check the dashboard's credit balance before retrying a 429, since it may mean the month is spent\n4. Don't write geocodes to a database on Free or Starter\n5. Use bulk-geocode for addresses only, not POI names\n\n## Questions\n\n### Which is better for AI agents, HERE Location Services or Stadia Maps?\n\nStadia Maps scores 65.2 (B) on agent readiness against HERE Location Services's 58 (C), and leads in 5 of 7 scored categories. HERE Location Services leads on security \u0026 auth.\n\n### Do HERE Location Services and Stadia Maps need an API key?\n\nHERE Location Services takes an API key or an OAuth sign-in. Stadia Maps needs an API key.\n\n### Can an agent call HERE Location Services and Stadia Maps without installing anything?\n\nYes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Stadia Maps at https://api.stadiamaps.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.json, and with the fewest tokens: https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"here-location-services\", \"b\": \"stadia-maps\"}`. From a terminal: `anchor compare here-location-services stadia-maps`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/here-location-services.json and https://www.anchorterminal.com/api/v1/tools/stadia-maps.json\n\n## Other comparisons with HERE Location Services or Stadia Maps\n\n- [Amazon Location Service vs HERE Location Services](https://www.anchorterminal.com/compare/amazon-location-vs-here-location-services.md)\n- [Amazon Location Service vs Stadia Maps](https://www.anchorterminal.com/compare/amazon-location-vs-stadia-maps.md)\n- [ArcGIS Location Platform vs HERE Location Services](https://www.anchorterminal.com/compare/arcgis-vs-here-location-services.md)\n- [ArcGIS Location Platform vs Stadia Maps](https://www.anchorterminal.com/compare/arcgis-vs-stadia-maps.md)\n- [Azure Maps vs HERE Location Services](https://www.anchorterminal.com/compare/azure-maps-vs-here-location-services.md)\n- [Azure Maps vs Stadia Maps](https://www.anchorterminal.com/compare/azure-maps-vs-stadia-maps.md)\n- [Geoapify Location Platform + MCP vs HERE Location Services](https://www.anchorterminal.com/compare/geoapify-vs-here-location-services.md)\n- [Geoapify Location Platform + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/geoapify-vs-stadia-maps.md)\n- [Google Maps Platform + Grounding Lite MCP vs HERE Location Services](https://www.anchorterminal.com/compare/google-maps-platform-vs-here-location-services.md)\n- [Google Maps Platform + Grounding Lite MCP vs Stadia Maps](https://www.anchorterminal.com/compare/google-maps-platform-vs-stadia-maps.md)\n- [HERE Location Services vs LocationIQ](https://www.anchorterminal.com/compare/here-location-services-vs-locationiq.md)\n- [HERE Location Services vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-mapbox.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [HERE Location Services vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/here-location-services-vs-opencage.md)\n- [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md)\n- [HERE Location Services vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/here-location-services-vs-tomtom.md)\n- [LocationIQ vs Stadia Maps](https://www.anchorterminal.com/compare/locationiq-vs-stadia-maps.md)\n- [Mapbox APIs + MCP vs Stadia Maps](https://www.anchorterminal.com/compare/mapbox-vs-stadia-maps.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [OpenCage Geocoding API vs Stadia Maps](https://www.anchorterminal.com/compare/opencage-vs-stadia-maps.md)\n- [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md)\n- [Stadia Maps vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/stadia-maps-vs-tomtom.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "HERE Location Services vs Stadia Maps",
        "url": ""
      }
    ],
    "description": "Stadia Maps scores 65.2 (B) to HERE Location Services's 58 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "HERE Location Services C 58",
      "Stadia Maps B 65.2",
      "scores"
    ],
    "h1": "HERE Location Services vs Stadia Maps",
    "image": "https://www.anchorterminal.com/assets/og/compare-here-location-services-vs-stadia-maps.png",
    "path": "/compare/here-location-services-vs-stadia-maps",
    "published": "2026-10-01",
    "section": "tools",
    "title": "HERE Location Services vs Stadia Maps for AI agents (2026)",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/here-location-services-vs-stadia-maps"
  },
  "tokens": {
    "markdown": 2500,
    "slim": 680
  },
  "version": 1
}