Transport for Auckland, New Zealand

{
  "service_type": "platform",
  "base_url": "https://dev-portal.at.govt.nz",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Ocp-Apim-Subscription-Key",
    "in": "header"
  },
  "endpoints": [
    {
      "path": "/api/v1/gtfs",
      "method": "GET",
      "description": "Provides GTFS schedule data for Auckland public transport"
    },
    {
      "path": "/api/v1/gtfs-realtime",
      "method": "GET",
      "description": "Provides real-time vehicle positions, trip updates, and service alerts"
    },
    {
      "path": "/api/v1/geojson",
      "method": "GET",
      "description": "Provides geospatial data including routes, stops, and service areas"
    },
    {
      "path": "/api/v1/od",
      "method": "GET",
      "description": "Provides origin-destination travel data (likely for historical analysis)"
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Public access to GTFS and some real-time feeds with rate limits",
      "paid_tier": "Commercial licenses for real-time data, higher rate limits, and enhanced support (contact for pricing)",
      "terms": "Requires registration for API keys, acceptance of Terms of Use"
    }
  },
  "rate_limits": {
    "free_tier": "10 requests per minute",
    "paid_tier": "Negotiable",
    "details": "Based on Azure API Management, subject to change"
  },
  "capabilities": [
    "Public transport schedule and real-time data",
    "GTFS and GTFS-Realtime feeds",
    "Geospatial stops, routes, and trip data",
    "Origin-destination travel matrices",
    "Developer portal with documentation and API key management",
    "Support for Auckland Transport's open data initiatives"
  ],
  "raw_analysis": "The Auckland Transport Developer Portal is a specialized platform providing access to Auckland's public transport data. It serves developers, researchers, and businesses interested in integrating transit information into their applications or conducting urban mobility analysis. The portal is part of Auckland Transport's open data strategy, offering both static GTFS (General Transit Feed Specification) and real-time GTFS-Realtime feeds. It also provides geospatial data (GeoJSON) for stops and routes, and origin-destination (OD) data for travel patterns. The platform is built on Microsoft Azure API Management (evident from the subscription key header 'Ocp-Apim-Subscription-Key'), indicating a mature and manageable API infrastructure. Authentication is via API key, which requires registration on the portal. Pricing is freemium: free access to static GTFS and limited real-time data with rate limits (likely 10 req/min for free tier), while commercial use requiring higher limits and/or real-time data may require a paid license, with terms subject to negotiation. The platform is primarily a data API provider, not a full transit management or monitoring dashboard, but it supports interoperability with standard transit apps (e.g., Google Maps, transit planning apps) due to GTFS compliance. Integrations are external via standard feeds; no built-in integrations are offered. The platform is mature and actively maintained, as it is operated by the Auckland Transport authority, ensuring reliability and up-to-date data. However, documentation is limited to the portal, and no public REST API beyond the provided endpoints is apparent. The target audience includes local developers, researchers, and transport-related enterprises. Overall, it's a solid open data platform for Auckland's transit ecosystem."
}

1/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.5,
    "response_parseability": 8.5,
    "error_clarity": 5.0,
    "doc_quality": 6.5,
    "auth_simplicity": 5.5,
    "latency": 7.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "free_tier": "Public GTFS and some real-time feeds with rate limits",
    "paid_tier": "Commercial licenses for real-time data, higher rate limits, enhanced support",
    "registration_required": true,
    "api_key_required": true
  },
  "issues": [
    "No robots.txt file (404) — may hinder indexing or signal incomplete site configuration",
    "No llms.txt file (404) — not optimized for AI agent discovery",
    "Requires manual registration and API key management, no SSO/magic link mentioned",
    "Pricing for paid tier is contact-based, not transparent"
  ],
  "recommendations": [
    "Add robots.txt and llms.txt for better agent discoverability",
    "Consider SSO or magic link authentication to simplify onboarding",
    "Publish transparent pricing for paid tiers",
    "Add clear error documentation for API limits and authorization failures"
  ]
}
```