{
 "categories": [
  "public-sector",
  "government",
  "data-exchange"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-10",
   "fact": "homepage",
   "note": "The current Entur for Developers portal presents getting-started guidance and an API catalogue. Content is marked as under active development. The previous portal remains at old.developer.entur.org.",
   "source": "https://developer.entur.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "vendor",
   "note": "The still-open legacy portal states that Entur operates the national registry for all public transport in Norway, collecting data from 60 operators, with about 21,000 daily departures on 3,000 routes, open and free of charge.",
   "source": "https://developer.entur.org/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "license",
   "note": "Journey Planner is documented as an Open Service licensed under NLOD. Open services need no partnership agreement.",
   "source": "https://developer.entur.no/docs/open-services/journey-planner",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.exists",
   "note": "Entur documents open public-transport data APIs (journey planner, mobility, real-time vehicle positions, stops and infrastructure) and partner sales/operator APIs.",
   "source": "https://developer.entur.no/docs/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.kinds[0]",
   "note": "Journey Planner v3 is a Transmodel-based GraphQL API. The only endpoint is POST https://api.entur.io/journey-planner/v3/graphql.",
   "source": "https://developer.entur.no/docs/open-services/journey-planner",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.kinds[1]",
   "note": "The open API catalogue also lists REST services including Geocoder, distances and zones, Stop Place Register, and timetable import info, alongside GraphQL Journey Planner, Mobility, and Vehicle Positions.",
   "source": "https://developer.entur.no/apis/open",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.auth[0]",
   "note": "Every Entur API, open and partner, requires the ET-Client-Name header in the form company-application. Requests without it may be rate limited or blocked. Open Geocoder calls need this header and no OAuth token.",
   "source": "https://developer.entur.no/docs/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.auth[1]",
   "note": "Partner APIs require OAuth 2.0 client_credentials. Clients created in Entur Partner exchange client_id and client_secret at https://partner.entur.org/oauth/token for a JWT that is sent as Authorization: Bearer. Tokens are valid 24 hours. Audience for production is https://api.entur.io.",
   "source": "https://developer.entur.no/docs/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.coverage",
   "note": "Open services cover journey planning, stop places, vehicle positions, mobility, and real-time data without a partnership. Entur also publishes static NeTEx timetable exports, stop-place data, and bulk real-time feeds.",
   "source": "https://developer.entur.no/docs/open-services",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.coverage",
   "note": "Partner services cover timetable upload/download, real-time deviations, and ticket sales. They require a partnership agreement, ET-Client-Name, and OAuth 2.0. That gate keeps overall coverage partial.",
   "source": "https://developer.entur.no/docs/partner-services",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.api.docs",
   "note": "Opened as the current getting-started guide for open versus partner access, ET-Client-Name, and the first Geocoder call.",
   "source": "https://developer.entur.no/docs/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.data_access.export[0]",
   "note": "Journey Planner accepts a JSON body with query and optional variables and returns GraphQL JSON.",
   "source": "https://developer.entur.no/docs/open-services/journey-planner",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.data_access.export[1]",
   "note": "The docs index lists daily updated timetable data dumps for public transport in Norway in NeTEx and GTFS formats.",
   "source": "https://developer.entur.no/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.data_access.export[2]",
   "note": "The docs index lists daily updated stop-place data dumps and GTFS-RT / SIRI real-time feeds alongside the NeTEx/GTFS timetable dumps.",
   "source": "https://developer.entur.no/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened https://developer.entur.no/llms.txt. It is a first-party documentation index with Markdown links for open services, partner APIs, and open-data dumps.",
   "source": "https://developer.entur.no/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "verdict.scores.api",
   "note": "Open GraphQL and REST APIs are documented, national in coverage, and usable without a partnership. Identified Journey Planner clients get 500 trip-requests per minute and 150 per second; 429 responses include quota headers. Sales and timetable write APIs stay behind a partnership and OAuth. That is the 7-8 band with material rate and partner-write limits.",
   "source": "https://developer.entur.no/docs/open-services/journey-planner/rate-limiting",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Entur for Developers home, with a pointer to old.developer.entur.org.",
   "source": "https://developer.entur.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current getting-started page for ET-Client-Name and open versus partner access.",
   "source": "https://developer.entur.no/docs/getting-started",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current OAuth 2.0 client-credentials guide for partner APIs, last modified 2026-09-01.",
   "source": "https://developer.entur.no/docs/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current Journey Planner v3 GraphQL page, including the production endpoint and NLOD statement.",
   "source": "https://developer.entur.no/docs/open-services/journey-planner",
   "tier": "declared"
  },
  {
   "date": "2026-09-10",
   "fact": "freshness.watch[4].url",
   "note": "Opened and verified as the current Entur docs llms.txt index.",
   "source": "https://developer.entur.no/llms.txt",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-10",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://developer.entur.no/"
   },
   {
    "type": "docs",
    "url": "https://developer.entur.no/docs/getting-started"
   },
   {
    "type": "docs",
    "url": "https://developer.entur.no/docs/authentication"
   },
   {
    "type": "docs",
    "url": "https://developer.entur.no/docs/open-services/journey-planner"
   },
   {
    "type": "docs",
    "url": "https://developer.entur.no/llms.txt"
   }
  ]
 },
 "homepage": "https://developer.entur.no/",
 "id": "entur",
 "license": "free",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "et-client-name",
    "oauth2-client-credentials"
   ],
   "coverage": "partial",
   "docs": "https://developer.entur.no/docs/getting-started",
   "exists": true,
   "kinds": [
    "graphql",
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "graphql-json",
    "netex",
    "gtfs"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Entur.no is a traveller web and app surface. The documented machine path is the developer APIs on developer.entur.no, not browser control of the travel planner.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Entur",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Entur",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 7,
   "rpa": null
  },
  "summary": "Entur is automatable today through its open national public-transport APIs, not as NVDB or a municipal ticket app. Journey Planner v3 is a Transmodel GraphQL API at https://api.entur.io/journey-planner/v3/graphql for routing and departure boards across Norwegian operators, including real-time. Geocoder, Stop Place Register, Mobility, and Vehicle Positions are additional open services. All open calls require the ET-Client-Name header. Identified Journey Planner clients are limited to 500 trip-requests per minute and 150 per second; unidentified traffic is tighter. Partner timetable, deviation, and sales APIs add OAuth 2.0 client-credentials against partner.entur.org and an Entur partnership agreement. First-party MCP ownership is not established. Names that only share the word \"venture\" are not this product. Computer-use viability is unassessed.\n"
 }
}