You are weeks into building something that moves people. Maybe it is a trip planner, maybe a fleet tool, maybe a ticketing app. You search the Transit tag on APIs.io and the two providers ranked first are HERE and Entur. You assume they are rivals in the same lane. They are not, and the difference decides which one you should build on.
HERE is a commercial location platform that sells maps, routing and positioning into more than 160 million vehicles. Entur is the Norwegian state-owned company that runs the national journey planner and the public-transport data platform for all of Norway. On the Kin Score, which measures the public API surface each one publishes and not the product or the company, HERE scores 77.6 and Entur 69.6. Both sit in the exemplar band. The gap is 8.0 points, and you want to know what it is made of.
The answer is that each side wins three facets by wide margins, in opposite directions. 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 covers versioning, ownership and change discipline on the contracts themselves. It also wins contract quality, 74.6 to 55.4, and developer ergonomics, 73.2 to 70.8.
The business models explain some of this. HERE sells a hosted service under a commercial license, and its record holds one pricing plan document and six rate-limit entries, though no published onboarding path or trial. It sells 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.
By page count they are closer than the composite suggests. HERE publishes 139 API pages and Entur 199. Entur's front door is GraphQL, with narrower REST APIs for sales, pricing and authentication behind it. Entur carries 196 contracts, none of them derived by the catalog, 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. That is worth knowing before you credit its total.
Here is the turn you should not skip. The catalog is candid about its own hand in these numbers. The composite gap has an asterisk on it: the conditional layers add 8.5 to HERE and 6.7 to Entur, but they are not computed over the same rules. HERE is scored against the horizontal regulatory regime at 35.3, Entur against Government and 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 agentic-access profiles on both, 743 operations for HERE and 922 for Entur, and the agent skills on both, were derived by the catalog, so neither company earns credit for them.
On 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 lights, documented delegated identity, through its OAuth authorization-code and client-credentials flows. Each lists one MCP server, but they are different things. HERE's is a remote documentation server, and Entur's is a proof of concept that wraps the journey planner and geocoder.
So what do you do with your project? If you need 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.
You also come away knowing what each provider could fix. Entur's number would move almost entirely on one facet: publishing its plans, quotas and sign-up path for partner services in a form a machine can read would close much of that 60.5-point 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 the catalog to derive.
Read the original: https://apis.io/2026/11/14/here-vs-entur-sixty-points-of-access-clarity-against-forty-five-of-governance/