Agent readiness · Maps and geocoding
here.com
8 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://docs.here.com/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript22,371 characters of text without JS, on https://docs.here.com/here-kb/docs/matrix-v8-postman-curl-examples-apikey-authentication rather than on https://docs.here.com/
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceMCP mentioned 1x in your own files, but nothing answered at mcp.here.com, mcp.here.com/mcp, mcp.here.com/v1/mcp, api.here.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://platform.here.com/portal/sign-up?step=verify-identity&aid=www.here.com-top-nav-start-building is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://platform.here.com/portal/sign-up?step=verify-identity&aid=www.here.com-top-nav-start-building is reachable, but its form needs JavaScript
D · Provisioning
- PASSProgrammatic key provisioning2 of 7 provisioning phrases across the 5 documents we read: "management api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
- FAILFree tier or no-card trial stated in texthttps://here.com/pricing carries a "start for free" style link and nothing else about a free tier, so what we found is a button rather than a stated price
E · Integration
- UNMEASUREDTyped SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://docs.here.com/here-kb/docs/matrix-v8-postman-curl-examples-apikey-authentication
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for here.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.