The two providers ranked first on the Transit tag are not the same kind of company. HERE is a commercial location platform that sells maps, routing and positioning into more than 160 million vehicles, and Entur is the Norwegian state-owned company that runs the national journey planner and the public-transport data platform for all of Norway. HERE scores 77.6 on the Kin Score and Entur 69.6, both in the exemplar band, and the score measures the public API surface each one publishes, not the product and not the company. The question for a reader building something that moves people is what that 8.0-point gap is made of, and the answer is that each side wins three facets by wide margins in opposite directions.
The business. HERE sells a hosted service, called at its endpoints, under a commercial license, and the record holds one pricing plan document and six rate-limit entries but no published onboarding path or trial. What it sells is breadth: geocoding, routing, traffic, weather, parking, tracking and an HD map for automated driving, with public transit as one product among a dozen. Entur sells tickets to travellers and gives the data away to developers: its open services, the journey planner, geocoder, real-time vehicles and shared mobility, are free, and partner services sit behind authentication. One is a location vendor with a transit API; the other is a transit authority with an API program.
The APIs. By page count they are closer than the composite suggests: HERE publishes 139 API pages and Entur 199. HERE’s include the Geocoding and Search API, the Tour Planning API, the Public Transit API and the Tracking API. Entur’s front door is GraphQL: the Journey Planner, Vehicle Positions and Mobility, behind which sit dozens of narrower REST APIs for sales, pricing and authentication. Entur carries 196 contracts, none of them derived by us, and 180 JSON Schema files where HERE has none. HERE carries 121 contracts, and 13 of them were derived by API Evangelist rather than published by HERE, which is worth knowing before crediting its total. Each lists one MCP server, and they are different things: HERE’s is a remote documentation server at docs.here.com, Entur’s is a proof of concept in its own GitHub org that wraps the journey planner and geocoder.
The experience, facet by facet. HERE wins access clarity 81.6 to 21.1, a 60.5-point gap and the widest in the comparison: how you get a key, what it costs and what you are allowed to do are written down for HERE and largely are not for Entur. HERE also wins operational transparency 92.1 to 63.2 and discoverability 90.0 to 80.0. Entur wins contract governance 76.5 to 31.8, a 44.7-point gap, which is versioning, ownership and change discipline on the contracts themselves, and it wins contract quality 74.6 to 55.4 and developer ergonomics 73.2 to 70.8. Contract quality carries the heaviest weight at 0.25, but access clarity at 0.20 is where the biggest number lives, and on the six weighted facets HERE leads 69.1 to 62.9. The conditional layers then add 8.5 to HERE and 6.7 to Entur, and they are not computed over the same rules: HERE is scored against the horizontal regulatory regime at 35.3, Entur against Government & Public Sector at 40.2, and HERE’s upsert score of 61.1 against Entur’s 33.3 accounts for most of the difference between the two lifts. The composite gap has that asterisk on it.
Agent readiness. HERE scores 55.5 and is agent-native; Entur scores 44.9 and is agent-ready. The band is gated, not read off the score, and the gate here is idempotency: HERE’s is verified, Entur’s is documented. HERE also publishes a well-known catalog and a dry-run mode that Entur does not. Entur takes the one identity dimension either of them lights, documented delegated identity, through its OAuth authorization-code and client-credentials flows. The agentic-access profiles on both, 743 operations for HERE and 922 for Entur, and the agent skills on both, were derived by us, so neither company earns credit for them.
The verdict. If you are building a commercial product that needs routing, maps and location across many countries, and you need to know up front what access costs, HERE’s surface is the clearer one to buy into. If you are building on Norwegian public transport, Entur is the source, its contracts are the better-governed and better-specified of the two, and the data is free. What would move Entur’s number is almost entirely one facet: publishing its plans, quotas and sign-up path for partner services in a form a machine can read would close much of a 60.5-point access-clarity gap, and verifying idempotency on its write operations would carry it across the agent-native gate. HERE’s path runs the other way, through versioning and change discipline on contracts it should be publishing itself rather than leaving for us to derive.