Yapi

{
  "service_type": "platform",
  "base_url": "http://yapi.smart-xwork.cn",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "Self-hosted open-source platform, free to deploy. No public SaaS pricing shown for this specific instance."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "API interface management",
    "API documentation generation",
    "Mock server",
    "Automated testing",
    "Team collaboration (front-end, back-end, QA)",
    "Visual interface design",
    "Local/private deployment",
    "Data import/export (Swagger, Postman, etc.)",
    "Permission and user management"
  ],
  "raw_analysis": "YApi is an open-source, visual API management platform originally developed by the Qunar team (YMFE). It is designed to unify API development workflows across front-end, back-end, and QA teams. The platform allows teams to design, document, mock, and test APIs in one place. It is commonly self-hosted, as indicated by the '可本地部署的' (locally deployable) description. The public instance at http://yapi.smart-xwork.cn appears to be a specific deployment for 'smart-xwork'; it may require authentication to access project data, but no public REST API documentation is provided. YApi itself includes an internal REST API for its web UI, and supports integrations like Swagger, Postman, and IDE plugins, but these are not exposed as a standard public API for third-party consumption. The platform is mature and widely used in Chinese tech companies for internal API governance."
}

1/3 tests passed

```json
{
  "overall": 61,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 5.5,
    "auth_simplicity": 4.0,
    "latency": 9.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "self-hosted open-source",
    "public_saas_pricing": false,
    "note": "Free to deploy locally; no public SaaS pricing for this instance"
  },
  "issues": [
    "Root URL returns 401 with a meta-refresh redirect instead of a helpful landing or auth prompt — unclear to users what this is",
    "No llms.txt (returns 401), reducing agent-discoverability of capabilities",
    "No security headers on responses",
    "Auth/signup flow is opaque from the public surface; appears to require a deployed instance, not self-serve onboarding",
    "robots.txt disallows dotbot but is minimal — limited crawl guidance",
    "Pricing model unknown for this instance, which complicates user recommendations"
  ],
  "recommendations": [
    "Serve a clear public landing page describing the platform's value prop (API management, docs generation, mock server, testing) without requiring auth",
    "Add an llms.txt and curl-friendly endpoints so agents can enumerate capabilities",
    "Document the onboarding path explicitly (self-host steps, default admin credentials, magic-link/SSO support)",
    "Add standard security headers (CSP, HSTS, X-Content-Type-Options)",
    "Publish a clear pricing/licensing statement (open-source license, commercial support options) to simplify recommendation",
    "Return structured JSON errors on 401 instead of HTML meta-refresh pages for API consumers"
  ]
}
```