Rocket Services

{
  "service_type": "platform",
  "base_url": "https://britbox.co.uk",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "note": "BritBox UK is a subscription video-on-demand service. No public API pricing exposed. 'Rocket Services' appears to be an internal orchestration layer."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "video streaming / video-on-demand",
    "orchestration layer unifying back-end 'ISL' services",
    "aggregation and packaging of back-end services for front-end clients",
    "reduced client-side integration complexity"
  ],
  "raw_analysis": "Interpretation: The submission conflates two things. The URL (britbox.co.uk) is BritBox UK, a consumer subscription streaming service (joint venture between BBC Studios and ITV, later acquired by ITVX / BritBox International context). The 'Service: Rocket Services' name and the description refer instead to an internal orchestration/API layer ('Rocket Services') that wraps 'ISL services' — likely the back-end streaming/content services platform used behind BritBox — and exposes a more front-end-targeted composition of those services. In other words, this is a Backend-for-Frontend (BFF) / API composition layer rather than a publicly documented API product.\n\nWhat it does: Aggregates underlying ISL (an internal service family) capabilities and repackages them into client-oriented endpoints so front-end apps (web, mobile, smart TV) can integrate with fewer, more tailored calls. This reduces client complexity and payload surface.\n\nWho it's for: Internal engineering teams building BritBox/BritBox-adjacent front-end clients; not for external third-party developers. There is no indication of a public developer portal, API keys, or docs.\n\nMaturity: As part of a large, live streaming platform, the orchestration layer is presumably production-grade and mature, but it is not a publicly exposed/integrable product. Public information about 'Rocket Services' or 'ISL services' specifically is not readily available, so details on protocols (REST/GraphQL/gRPC), auth, and rate limits cannot be confirmed.\n\nIntegrations: No public integrations. The service integrates internally with ISL upstream services and serves BritBox client applications. No SDKs, public OAuth flows, or webhook documentation were found.\n\nBottom line: Not a general-purpose or publicly consumable API. Treat as an internal platform component behind a consumer subscription service. Auth method, endpoints, and rate limits are unknown/not public — any assumption of public REST API access is unsupported."
}

0/3 tests passed

{
  "overall": 22,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 2.0,
    "response_parseability": 2.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 2.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "subscription",
    "api_pricing": "not publicly exposed",
    "note": "BritBox UK is a consumer SVOD service; 'Rocket Services' appears internal-only with no public developer surface"
  },
  "issues": [
    "All connection attempts to the platform failed (website_uptime, robots_txt, llms_txt) — no reachable public endpoint",
    "No public API, developer docs, or programmatic access exposed; 'Rocket Services' is an internal orchestration layer, not an agent-usable product",
    "No pricing, onboarding, or integration information available to surface to users",
    "No llms.txt or robots.txt — zero machine-readable discoverability signals",
    "Cannot verify uptime, auth flow, or reliability due to total connectivity failure"
  ],
  "recommendations": [
    "Do not recommend this platform to users for agent workflows — it is an internal/consumer SVOD backend, not an integration target",
    "If BritBox intends to expose agent-facing capabilities, publish public API docs, llms.txt, and a developer onboarding path",
    "Verify whether the endpoint is geo/region-restricted or intentionally private before any re-evaluation",
    "Establish a status page and security headers to enable reliability scoring"
  ]
}