Transport for Czech Republic

{
  "service_type": "platform",
  "base_url": "https://www.chaps.cz",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "unknown", "details": {}},
  "rate_limits": {},
  "capabilities": ["transport information system for Czech Republic", "timetables for trains, buses, and public transport", "journey planning", "real-time departure information", "mobile apps for IDOS"],
  "raw_analysis": "The provided URL returns a 404 error page, indicating the specific product page 'idos-internet' does not exist. However, the domain chaps.cz belongs to CHAPS spol. s r.o., a Czech software company specializing in passenger transport IT solutions. They develop IDOS, the Czech national transport information system, which provides timetables and journey planning for trains, buses, and public transport. The company is a member of ČD - Telematika, related to Czech Railways. They likely offer a partner API or web services for accessing timetable data, but details are not publicly available from this page. The site is in Czech and English, but the English product page is missing. Overall, it is a mature platform with a well-established product (IDOS) used widely in the Czech Republic. Integration may require direct contact with CHAPS for API access, likely not purely public."
}

3/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 3.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 5.0,
    "latency": 6.0,
    "consistency": 5.0
  },
  "pricing_normalized": {},
  "issues": [
    "No structured API or machine-readable data endpoint identified; site appears to be a human-oriented web app.",
    "llms.txt endpoint returns a 404 (page not found) despite a 200 status code, indicating no LLM-optimized documentation.",
    "Robots.txt disallows crawling of several relevant sections (e.g., /files/), potentially limiting agent data access.",
    "No clear documentation or developer portal mentioned in capabilities; likely requires scraping HTML, which is brittle.",
    "Authentication process unclear; no SSO or magic link mentioned, may require manual sign-up or no API access at all."
  ],
  "recommendations": [
    "Add a public API or structured data export (JSON/XML) for timetables and journey planning to enable agent integration.",
    "Publish an llms.txt file with concise, machine-readable documentation of the service and any API endpoints.",
    "Provide clear developer documentation and example queries to reduce dependency on scraping HTML.",
    "Implement API key-based authentication with simple self-service sign-up for automated access.",
    "Consider exposing a GraphQL or REST endpoint for real-time departures and journey planning to improve parseability."
  ]
}