Mobility API

{
  "service_type": "platform",
  "base_url": "https://o2.cz:mobility",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Transit mobility data",
    "Time-aggregated population movement data",
    "Origin-destination (A-to-B) mobility queries",
    "Spatial analysis within Czech Republic"
  ],
  "raw_analysis": "The Mobility API is described as a transit/mobility data service provided in connection with O2 Czech Republic (o2.cz). It provides time-aggregated data representing the movement of people between spatial points (A to B) within the Czech Republic. Based on the URL pattern 'o2.cz:mobility', this appears to be a service hosted on or associated with the O2 Czech Republic platform rather than a standard REST API with a publicly documented base URL. The colon notation suggests a platform-internal identifier or a non-standard URL scheme, not a conventional HTTPS REST endpoint.\n\nWhat the platform does: It aggregates anonymized mobility/transit data derived likely from mobile network signals (O2 is a major Czech telecom operator), returning aggregated origin-destination flow data between geographic points in the Czech Republic. This is characteristic of telco-derived mobility data products used for urban planning, transportation analysis, tourism statistics, and smart-city applications.\n\nWho it's for: Likely enterprise customers, government/municipal agencies, researchers, transportation planners, and data analysts studying population movement in the Czech Republic.\n\nMaturity: The description is truncated ('the API can retur...'), suggesting incomplete documentation in the source listing. No public REST API documentation, endpoint listings, or authentication details are provided. The maturity level is difficult to assess from the available information; it appears to be an internal or partner-only data service rather than a self-service public API.\n\nIntegrations: No known public integrations or SDKs are documented. Access is likely gated behind a business agreement with O2 Czech Republic.\n\nLimitations: The provided URL format (o2.cz:mobility) is not a valid REST base URL. Authentication method, pricing, rate limits, and specific endpoints could not be determined from the available description. Users would need to contact O2 Czech Republic directly to obtain API access details and documentation."
}

0/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 2.0,
    "response_parseability": 4.0,
    "error_clarity": 2.0,
    "doc_quality": 3.0,
    "auth_simplicity": 3.0,
    "latency": 2.0,
    "consistency": 3.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "tiers": [],
    "note": "No pricing information could be retrieved; URL resolution failed."
  },
  "issues": [
    "All three validation checks failed with 'Invalid port: mobility' — the platform URL appears malformed or unresolvable, blocking any concrete assessment.",
    "No website, robots.txt, or llms.txt content could be fetched, meaning no verifiable documentation, onboarding, or API surface was confirmed.",
    "Pricing model is unknown; no pricing page or tier information was accessible.",
    "Latency measurements (185ms, 6ms, 8ms) are artifacts of immediate parse failures, not real network timings — do not reflect actual server responsiveness.",
    "Value proposition (Czech origin-destination transit mobility data) is inferred from metadata only, not confirmed from primary sources."
  ],
  "recommendations": [
    "Fix the canonical domain/port configuration so agents can resolve the platform endpoint (e.g., https://mobility.example.cz without stray port segments).",
    "Publish a machine-readable llms.txt and robots.txt to enable agent onboarding and crawling.",
    "Provide a public pricing page or explicit 'contact sales' marker so agents can communicate cost expectations.",
    "Expose a documented REST or GraphQL API with schema and example queries for origin-destination mobility lookups.",
    "Add a getting-started guide with signup flow, auth method (API key, OAuth, or magic link), and rate limits.",
    "Maintain a status page with uptime history to support consistency and reliability scoring.",
    "Since this is Czech Republic–scoped mobility data, document geographic coverage, time granularity, and licensing terms clearly."
  ]
}