Weex

{
  "service_type": "platform",
  "base_url": "https://weexapp.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "Weex is an open-source framework, free to use"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "cross-platform mobile UI development",
    "write once, run on iOS/Android/Web",
    "Vue.js-style component model",
    "native rendering via native components",
    "JavaScript runtime with native bridge",
    "hot reloading and dynamic updates",
    "open-source with community contributions"
  ],
  "raw_analysis": "Weex is an open-source cross-platform mobile UI framework originally developed by Alibaba. It allows developers to write user interfaces using web technologies (HTML/CSS/JavaScript, with a Vue.js-inspired syntax) that compile to native components for iOS, Android, and Web. It was designed for building performant, native-feeling mobile applications with a single codebase.\n\nMaturity: Weex was actively developed around 2016-2019, saw adoption in Alibaba's apps (Taobao, Tmall, Alipay) and beyond. However, as of recent years, development has significantly slowed, and the project is largely in maintenance mode. The official documentation and community activity have diminished. It has been largely superseded by frameworks like React Native and Flutter, as well as Alibaba's own newer solutions (e.g., Rax, Mini Program containers).\n\nTarget users: Mobile developers looking for a cross-platform UI solution, particularly those in the Chinese ecosystem or within Alibaba-affiliated projects.\n\nIntegrations: Weex integrates with Vue.js, supports native module extensions, and has tooling for bundling and debugging (weex-toolkit, weex-devtool). It can be embedded into native apps as a runtime.\n\nThe provided content is an error page from Taobao (淘宝网) indicating that weexapp.com likely redirected or is no longer serving the original content. The domain may have lapsed or been repurposed. The actual Weex project is hosted on GitHub (alibaba/weex) and has documentation at weex.apache.org (now archived) and previously weex.io.\n\nAPI: Weex is a framework, not a SaaS platform, so it does not expose a public REST API. Integration is done at the code level via SDKs and native bridges. There is no authentication or rate limiting applicable to the framework itself.\n\nGiven the state of the domain and the project, it is recommended to treat Weex as a legacy technology. No active API endpoints exist."
}

3/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 4.0,
    "response_parseability": 4.5,
    "error_clarity": 5.0,
    "doc_quality": 5.0,
    "auth_simplicity": 9.0,
    "latency": 6.0,
    "consistency": 4.5
  },
  "pricing_normalized": {
    "model": "free",
    "open_source": true,
    "note": "Weex is a free, open-source framework — no pricing tiers or billing complexity for agents to explain."
  },
  "issues": [
    "The 'robots_txt' and 'llms_txt' check endpoints returned HTML instead of plain-text robots.txt / llms.txt content, indicating these paths are not properly served — agents and crawlers get no machine-readable guidance.",
    "No structured API surface detected; Weex is a UI framework/SDK rather than a service platform, so 'response_parseability' is inherently limited.",
    "Website latency ~958ms on the primary page exceeds the <500ms ideal, though robots/llms paths were faster (360-411ms).",
    "Weex is largely a dormant/legacy project (superseded by Flutter/React Native) — consistency and long-term maintenance perception are weak."
  ],
  "recommendations": [
    "Serve a real /robots.txt and /llms.txt with plain-text content so agents can parse platform rules and capabilities without HTML noise.",
    "Publish a concise, machine-readable capability/API summary (JSON or OpenAPI-style) so agents can describe value props without scraping HTML.",
    "Add explicit docs on limitations (platform support status, maintenance cadence) given Weex's legacy standing versus newer competitors.",
    "Improve primary page latency below 500ms to strengthen first-impression reliability."
  ]
}