Sreworks

{
  "service_type": "platform",
  "base_url": "https://sreworks.cn",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No pricing information available. Project appears to be open source (hosted/linked to Alibaba Open Source ecosystem), so likely free to self-host."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Cloud Native DataOps",
    "Cloud Native AIOps",
    "Operations automation",
    "Observability and monitoring integration",
    "Open source platform (Alibaba ecosystem)"
  ],
  "raw_analysis": "Sreworks (sreworks.cn) is presented as a 'Cloud Native DataOps & AIOps Platform' (云原生数智运维平台). It targets operations/DevOps teams seeking data-driven and AI-driven operations management in cloud-native environments.\n\nThe only retrievable content is an HTML redirect/404 handler page whose scripts reference Alibaba CDN resources (cdn.bootcss.com, g.alicdn.com, opensource.alibaba.com). The script logic: if the requested path is '/', redirect to https://opensource.alibaba.com/ (Alibaba Open Source homepage); otherwise redirect to /404.html on the same base. This strongly indicates that sreworks.cn is now defunct, deprecated, or has been folded back into Alibaba's open source umbrella. The domain no longer serves its own application or documentation.\n\nNo public REST API endpoints, authentication mechanisms, rate limits, or pricing details are discoverable from the available content. Given the redirect to Alibaba Open Source, this was likely an open-source, self-hostable platform (no SaaS REST API), with its code and docs previously hosted under Alibaba's open source projects (possibly related to DataOps/AIOps tooling). \n\nMaturity assessment: The project URL is effectively dead/redirecting, which implies it is either retired, renamed, or migrated. Integration capabilities cannot be confirmed. Anyone evaluating this platform should look at Alibaba's open source organization (opensource.alibaba.com) or GitHub for any successor or archived repository.\n\nRecommendation: Treat as inactive/deprecated from a public-API integration standpoint. No actionable endpoints or auth flow exist at the given URL."
}

3/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.5,
    "response_parseability": 4.0,
    "error_clarity": 3.0,
    "doc_quality": 5.5,
    "auth_simplicity": 5.0,
    "latency": 6.5,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "note": "No pricing page detected; likely open source self-hosted (Alibaba OSS ecosystem), no defined agent-relevant pricing tier",
    "tiers": []
  },
  "issues": [
    "Primary site returns Docusaurus v2.0.1 docs in Chinese (lang=zh) — token/persona mismatch for English-speaking agent consumers",
    "robots.txt check returned an HTML page (not a plain-text robots file) — endpoint misimplementation or CDN rewrite, breaks standard crawler contract",
    "llms_txt check returned the same generic 404-style redirect stub — no llms.txt present, so agents get no machine-readable platform summary",
    "No security headers reported on any checked response (missing CSP, HSTS, X-Content-Type-Options)",
    "Pricing model unclear — no public pricing, no license summary surfaced in checks, blocking cost-comparison recommendations",
    "Capabilities are broad but vague ('Cloud Native DataOps/AIOps', 'Operations automation') — hard to map to a concrete user need without digging into docs",
    "robots.txt / llms.txt returning an obfuscated 'not found → redirect' HTML page suggests fragile edge routing that agents cannot deterministically parse"
  ],
  "recommendations": [
    "Add a proper /llms.txt with a concise English + Chinese platform summary, capability list, and link map — directly improves token efficiency and first-try success",
    "Serve a real text/plain robots.txt instead of an HTML redirect stub; standard crawler behavior is expected by agent tooling",
    "Publish a short English 'What is this' landing page fronting the Chinese docs, with explicit use cases (DataOps vs AIOps vs automation) so agents can match it to user intents",
    "Clarify license and pricing/self-host story on a single page — critical for agent recommendations that must weigh cost",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) and a /status or health endpoint so agents can judge reliability",
    "Tighten latency (786ms for the main doc page is acceptable but not great) and stabilize edge routing so robots.txt/llms.txt don't route through the 404 handler"
  ]
}