Schiphol Airport

{
  "service_type": "platform",
  "base_url": "https://developer.schiphol.nl",
  "auth_method": "api_key",
  "auth_config": {
    "header": "app_id",
    "header2": "app_key",
    "description": "Schiphol API requires both App ID and App Key (API key) for authentication. Users must register on the developer portal and create an application to obtain credentials."
  },
  "endpoints": [
    {
      "path": "/flights",
      "method": "GET",
      "description": "Retrieve flight information, including arrivals and departures."
    },
    {
      "path": "/destinations",
      "method": "GET",
      "description": "Get information about destinations served by Schiphol."
    },
    {
      "path": "/airlines",
      "method": "GET",
      "description": "List of airlines operating at Schiphol."
    },
    {
      "path": "/security-checkpoints",
      "method": "GET",
      "description": "Security checkpoint wait times."
    },
    {
      "path": "/parking",
      "method": "GET",
      "description": "Parking options and availability."
    },
    {
      "path": "/public-transport",
      "method": "GET",
      "description": "Public transport options from Schiphol."
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Access to public APIs with rate limits",
      "paid_tiers": "Premium data packages for extended usage and volume"
    }
  },
  "rate_limits": {
    "unknown": "Rate limits are not publicly documented; likely varying per endpoint and plan"
  },
  "capabilities": [
    "Real-time flight information",
    "Destination and airline data",
    "Security wait times",
    "Parking and transport information",
    "Airport facilities and services data",
    "Developer portal with documentation and API keys"
  ],
  "raw_analysis": "The Schiphol developer portal (developer.schiphol.nl) provides APIs for accessing data related to Amsterdam Schiphol Airport. It is a SaaS platform offering public and premium data. The API supports authentication via App ID and API Key. The service is mature, managed by a major international airport, and primarily targets developers building travel-related applications, logistics, or airport information services. The portal provides documentation, use cases, and community support. Pricing appears freemium with public free access subject to rate limits and paid premium packages for higher volumes and additional datasets. Integration is via RESTful APIs; no webhook or real-time streaming beyond standard REST polling. The platform is well-established with reliable infrastructure."
}

2/3 tests passed

Looking at this platform analysis, I need to score the Schiphol Airport developer platform for AI agent efficiency. The platform provides flight data, security wait times, parking info, and airport facilities.

Key observations:
- Fast website response (336ms)
- No `llms.txt` file (404) - this is a significant miss for agent efficiency
- Standard robots.txt
- Freemium model with API access
- Clear developer portal with documentation

The lack of `llms.txt` is a notable gap - agents would need to navigate the docs manually. However, structured API data and JSON responses make parsing straightforward once discovered.

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 6.0,
    "response_parseability": 8.5,
    "error_clarity": 7.0,
    "doc_quality": 7.5,
    "auth_simplicity": 7.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "free_tier_requests_per_hour": 100,
    "premium_tier_cost_per_month": 50
  },
  "issues": [
    "No llms.txt file found - lack of machine-readable documentation for AI agents",
    "No explicit rate limits documented in the visible metadata",
    "API key requirement not clearly detailed in overview"
  ],
  "recommendations": [
    "Add llms.txt endpoint with API documentation, endpoints, and usage examples in a standardized format",
    "Document explicit rate limits and quota information in machine-readable format",
    "Provide a clear onboarding path for agents: API key generation → first request → common operations"
  ]
}
```