Smartphone Test Farm

{
  "service_type": "platform",
  "base_url": "http://openstf.io",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "OpenSTF is an open-source project, free to use and self-host."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Remote control of real Android devices via browser",
    "RESTful API for device management and automation",
    "Device reservation and sharing",
    "Screen mirroring and interaction",
    "ADB over network",
    "Device monitoring and health checks",
    "Support for multiple users and teams"
  ],
  "raw_analysis": "OpenSTF (Smartphone Test Farm) is an open-source platform that allows users to control and manage real Android devices remotely from a web browser. It provides a web interface and RESTful APIs for device interaction, making it suitable for mobile testing, development, and debugging. The platform is designed for developers, QA engineers, and teams needing access to physical devices. It is self-hosted and free to use. The website (openstf.io) appears to be a WordPress-based blog or landing page, with no direct API documentation available. The actual API is part of the self-hosted application, typically documented in the project's GitHub repository (https://github.com/openstf/stf). The platform is mature, with a large community and commercial support available through other vendors. Integrations include ADB, various CI systems, and custom scripts via REST API."
}

3/3 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 8.0,
    "error_clarity": 5.5,
    "doc_quality": 6.0,
    "auth_simplicity": 6.0,
    "latency": 5.0,
    "consistency": 5.5
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Open-source, free to self-host. No managed SaaS — user bears hosting, device provisioning, and ops cost."
  },
  "issues": [
    "robots.txt and llms.txt both return HTML (the homepage), not actual robots/llms directives — misconfigured routing, so agents can't discover crawl rules or agent-friendly docs.",
    "No security headers detected on any response; weak signal for production readiness.",
    "Latency ~1.0–1.4s per request — usable but not snappy for agentic loops.",
    "Self-hosted-only model means 'onboarding' actually means standing up infrastructure (Docker, ADB, device farm), which is far from minutes-to-productive.",
    "Website appears to be a WordPress marketing page; the actual product docs/API live elsewhere (GitHub), fragmenting the description agents must give users.",
    "No managed cloud offering or hosted API endpoint — agents can't just point users at a key and go."
  ],
  "recommendations": [
    "Fix robots.txt and llms.txt to return real plain-text directives (or at least valid content) so agent tooling can parse crawl/agent guidance instead of hitting the HTML homepage.",
    "Add a concise /llms.txt summarizing capabilities, self-host steps, REST API base, and ADB-over-network usage in machine-readable form.",
    "Publish a quickstart with a docker-compose one-liner and default credentials, plus an API reference (device list, reserve, connect) with example curl calls — this would sharply improve first_try_success.",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to signal production quality and improve trust scoring.",
    "Clarify limitations in docs: device compatibility matrix, ADB requirement, port/firewall needs, and concurrency limits.",
    "Consider a hosted/managed tier or a reference cloud deployment to remove the self-host tax and raise auth_simplicity from manual user provisioning to a simple API key or SSO."
  ]
}
```