Czech Television

{
  "service_type": "platform",
  "base_url": "http://www.ceskatelevize.cz",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/xml/tv-program",
      "method": "GET",
      "description": "Returns the current TV programme schedule for Czech Television channels in XML format. This is the primary resource for accessing schedule data."
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "description": "The XML TV programme endpoint is publicly accessible without any fees or subscription requirements. Czech Television is a public service broadcaster funded by mandatory licence fees, but the XML schedule service is free to use."
    }
  },
  "rate_limits": {
    "note": "No specific rate limits documented publicly. As a public broadcaster, they may expect reasonable usage, but there is no explicit policy visible. It is advisable to implement caching and avoid excessive polling."
  },
  "capabilities": [
    "Provides TV schedule data in XML format",
    "Covers Czech Television channels (e.g., ČT1, ČT2, ČT24, ČT sport, ČT :D, ČT art)",
    "Likely includes programme titles, start/end times, and possibly descriptions or categories",
    "Publicly accessible without authentication, making it suitable for lightweight integrations and mashups",
    "No official API documentation; it's a raw XML endpoint rather than a full-featured API"
  ],
  "raw_analysis": "Czech Television (Česká televize) is the public television broadcaster in the Czech Republic. Their website provides an XML endpoint at /xml/tv-program that returns the TV schedule for their channels. This is not a full REST API but a direct XML feed, typical for television schedule data. The service is very mature as Czech Television is an established institution, and the XML endpoint has been provided for years as a public resource. It appears to have no authentication requirements, making it easy to access. However, there are no published rate limits; typical usage would be periodic polling. The available data likely includes programme listings with details, but the XML structure is not documented, so developers may need to parse it. The service is free and targeted at developers who want to integrate TV schedules into applications or websites, especially for audiences in Czech-speaking regions. Integration potential is limited due to the lack of a formal API, but the XML feed can be used directly. There are no known official integrations or SDKs; it is raw data. The XML format is a standard, so it can be consumed by various programming languages. The platform does not offer other API features like registration, rate limit management, or rich metadata beyond the schedule. Overall, it is a simple, reliable, and free resource for Czech TV scheduling data."
}

3/3 tests passed

```json
{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 4.0,
    "response_parseability": 2.0,
    "error_clarity": 2.0,
    "doc_quality": 1.0,
    "auth_simplicity": 10.0,
    "latency": 5.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "type": "free",
    "notes": "Public service broadcaster XML endpoint - no cost but no SLA or support"
  },
  "issues": [
    "No official API documentation - it's a raw XML endpoint requiring reverse engineering",
    "No structured data format guarantees - XML schema unknown and may change without notice",
    "No error handling documentation - unclear how failures are communicated",
    "No rate limiting or usage guidelines documented",
    "Robots.txt explicitly disallows /ivysilani/api paths suggesting instability",
    "No llms.txt file - lacks machine-readable documentation",
    "No API status page or uptime guarantees",
    "Czech-language interface only - limited accessibility",
    "No versioning or deprecation policy for the XML feed"
  ],
  "recommendations": [
    "Document the XML schema with sample responses and field descriptions",
    "Add an llms.txt file with direct API documentation and usage limits",
    "Provide a formal API with versioning and error codes instead of raw XML",
    "Publish a status page with uptime history and incident communication",
    "Add English documentation to broaden accessibility",
    "Clarify rate limits and terms of use for the public XML endpoint"
  ]
}
```