Transport for Norway

{
  "service_type": "platform",
  "base_url": "https://developer.entur.org",
  "auth_method": "API key",
  "auth_config": {
    "header": "ET-Client-Name",
    "description": "Required for all APIs, a custom header identifying the client and contact info (e.g., 'company - application - email').",
    "location": "Header"
  },
  "endpoints": [
    "https://api.entur.io/journey-planner/v3/graphql",
    "https://api.entur.io/geocoder/v1",
    "https://api.entur.io/realtime/v1/vehicles",
    "https://api.entur.io/mobility/v1",
    "https://api.entur.io/stop-places/v1",
    "https://data.entur.io/",
    "https://api.entur.io/mobility/timetable/v1"
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Most APIs are free to use with an open data license (NLOD 2.0 / CC BY 4.0).",
      "paid_tier": "Some premium APIs (e.g., Journey Planner with higher reliability, flexible routing) may require a commercial agreement.",
      "registration": "No formal registration required, but users must use ET-Client-Name header with active email."
    }
  },
  "rate_limits": {
    "general": "No hard public limits documented, but high volume use is discouraged; may include soft limits per API.",
    "journey_planner": "Reasonable use policy: max 10 requests per second per client is suggested.",
    "geocoder": "Not strictly documented, but fair use expected."
  },
  "capabilities": [
    "Open data platform for Norwegian transport",
    "Journey planner API (multi-modal transit routing with GraphQL)",
    "Geocoder and reverse geocoder (address and stop search)",
    "Real-time vehicle positions, stop monitoring, and departure predictions",
    "Mobility services (scooters, bike share, car share APIs)",
    "Stop places register and map data (NeTEx/GTFS)",
    "Public transport dataset downloads (GTFS, NeTEx, SIRI)",
    "GraphQL and REST APIs",
    "Support for both historical and real-time data",
    "Tavla - open source display board (Entur's digital signage solution)",
    "Integrations with national transport networks in Norway",
    "Documentation portal with quick start guides, API reference, and changelog",
    "Open data license (NLOD) and partner services for paid support"
  ],
  "raw_analysis": "Transport for Norway, accessed via developer.entur.org, is the official open data platform by Entur, a Norwegian public transport administration. It provides national travel planning, real-time transit data, geocoding, and mobility services (shared bikes, scooters, etc.) through a set of well-documented APIs. The platform is mature and actively maintained, evidenced by a structured developer portal (built with Gatsby) including quick start guides, API reference, and a changelog with environment-specific updates. Core APIs include the Journey Planner (GraphQL), Geocoder (REST), Realtime (SIRI-based), Stop Places (NeTEx/GTFS), and Mobility APIs. Data is provided under open licenses (NLOD 2.0 / CC BY 4.0), making it free for non-commercial use; commercial use may require agreements. Authentication is minimal but requires a custom 'ET-Client-Name' header for traceability. There are no strict public rate limits, but fair use policies apply (e.g., max 10 requests per second for Journey Planner). The platform also offers downloadable static datasets (GTFS, NeTEx) and a companion 'Tavla' service for custom departure boards. This is ideal for developers building mobility apps, transport analytics, or travel solutions for Norway. It lacks a traditional OAuth flow but aligns with open data practices. The absence of a formal pricing page suggests a freemium model with partner agreements for premium reliability."
}

3/3 tests passed

```json
{
  "overall": 82,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 9.0,
    "response_parseability": 8.5,
    "error_clarity": 7.5,
    "doc_quality": 8.0,
    "auth_simplicity": 9.0,
    "latency": 10.0,
    "consistency": 9.0
  },
  "pricing_normalized": {
    "free_tier": "Open data license (NLOD 2.0 / CC BY 4.0) - no registration, just use ET-Client-Name header",
    "paid_tier": "Commercial agreements for premium Journey Planner APIs with higher reliability",
    "registration_requirement": "None formal, but ET-Client-Name header with active email required"
  },
  "issues": [
    "No llms.txt file found - SPA returns HTML for /llms.txt requests",
    "No robots.txt accessible - likely SPA redirects to index",
    "Authentication requirement (ET-Client-Name header) may not be immediately obvious to new users"
  ],
  "recommendations": [
    "Add an llms.txt file to improve agent discoverability and documentation",
    "Provide clear error responses when ET-Client-Name header is missing",
    "Add explicit API rate limits and usage guidelines to prevent abuse"
  ]
}
```