Openhands

{
  "service_type": "platform",
  "base_url": "https://openhands.dev",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "AI-driven software development",
    "Autonomous coding agent",
    "Development environment automation",
    "Code generation and modification"
  ],
  "raw_analysis": "OpenHands is an AI-driven development platform that appears to provide autonomous software engineering agents capable of performing coding tasks. Based on the URL https://openhands.dev and the tagline 'AI-Driven Development', the service targets software developers, engineering teams, and organizations looking to automate or augment coding workflows with AI.\n\nThe platform category is listed as 'developer, ai, api', suggesting it offers developer-focused AI tooling and potentially programmatic access. The project is likely related to the open-source OpenHands (formerly OpenDevin) initiative, which is an autonomous AI software engineer agent. However, the specific .dev domain may represent a hosted or commercial variant.\n\nMaturity is difficult to assess precisely from the provided metadata alone, but the existence of a dedicated .dev domain and a categorized listing implies an active project with some level of public presence. The use of an emoji and concise slogan is consistent with modern developer-focused product marketing.\n\nIntegrations are not specified in the provided data, but an AI coding agent of this nature typically integrates with development environments, version control systems (e.g., Git, GitHub), CI/CD pipelines, and cloud or local sandboxes. No public REST API documentation, authentication requirements, endpoints, pricing model, or rate limits are provided in the source content, so those remain unknown. Further investigation of the site's documentation would be required to determine API availability and access controls."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.5,
    "response_parseability_note": null,
    "latency": 8.5,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "unknown",
    "has_public_pricing": false,
    "note": "No pricing details detected — cannot normalize to per-token/per-seat cost."
  },
  "issues": [
    "No llms.txt (404) — agents lack a machine-readable entry point for capabilities/pricing/auth.",
    "Pricing model is 'unknown' with no public pricing surface detected; agents can't compare or recommend on cost.",
    "Docs/help quality signals are weak from checks alone — no dedicated developer docs endpoint verified.",
    "Auth flow is unverified; the card mentions 'Notlogin' but there's no evidence of SSO/magic-link/provider support on the endpoint checked."
  ],
  "recommendations": [
    "Publish an /llms.txt summarizing product, pricing, API surface, auth options, and rate limits for agent consumption.",
    "Add a stable, documented pricing page with programmatic (JSON) access so agents can quote costs accurately.",
    "Expose a public API doc (OpenAPI) and a status page URL in llms.txt to raise response_parseability and consistency scores.",
    "Clarify onboarding: document sign-up flow, supported auth providers (SSO, magic link, API keys), and time-to-first-call.",
    "Add explicit limitations/known-issues section to help docs to improve error_clarity.",
    "Note in robots.txt that ai-input=yes already encourages agent use — extend that signal to a structured capability manifest."
  ]
}