Lapce

{
  "service_type": "platform",
  "base_url": "https://lap.dev/lapce",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "model": "Open source, free to use",
      "repository": "https://github.com/lapce/lapce",
      "license": "Apache-2.0 / MIT (dual-licensed, check repo)"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Code editing",
    "Syntax highlighting",
    "LSP (Language Server Protocol) support",
    "DAP (Debug Adapter Protocol) debugger integration",
    "WASI-based plugin system",
    "Remote development",
    "Vim-style modal editing",
    "Terminal integration",
    "Built-in command palette",
    "Cross-platform (Linux, macOS, Windows)",
    "GPU-accelerated UI (Floem framework)",
    "Tree-sitter based syntax parsing"
  ],
  "raw_analysis": "Lapce is a free, open-source code editor written in Rust, positioned as a lightweight, high-performance alternative to editors like VS Code and Sublime Text. It targets developers who prioritize speed and a native, GPU-accelerated UI. The project is hosted on GitHub (lapce/lapce) and distributed under permissive open-source licenses. Maturity: it is an active but relatively young project; commonly used by early adopters and Rust enthusiasts. It has a growing plugin ecosystem based on WASI, and supports LSP and DAP for language intelligence and debugging. Remote development is supported, though it may require a companion 'lapce-proxy' binary.\n\nAPI surface: Lapce does NOT expose a public REST or HTTP API. There is no documented public API for programmatic control or integration. Interoperability is achieved through the plugin system (WASI), LSP, and DAP protocols rather than a web API. Any automation would need to be built via plugins or by interacting with the local editor process.\n\nPricing: entirely free and open source. No commercial tiers or hosted service (as of analysis). \n\nAuthentication: not applicable \u2014 no accounts or API keys.\n\nRate limits: not applicable.\n\nIntegrations: key integration points are LSP servers, DAP debug adapters, terminal shells, and WASI plugins. There is no known official REST API, webhook system, or cloud sync service.\n\nSummary for Prowl: Lapce is a desktop code editor, not a web service. It should be categorized as a local tool/platform with no network API. No endpoints, auth, or pricing plans (beyond free) are available."
}

1/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 5.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 9.0,
    "latency": 9.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "free",
    "tier": "open_source",
    "cost": 0
  },
  "issues": [
    "No llms.txt or robots.txt — agent crawlers and LLM-based tools get 404s, reducing discoverability",
    "No public API or structured data endpoints — it's a desktop editor, so agents can't programmatically interact",
    "Website preview suggests Lapdev marketing content (Kubernetes dev environments) mixed with Lapce editor branding — potential domain confusion or shared hosting",
    "No status page or uptime documentation surfaced",
    "Dual-license ambiguity (Apache-2.0 vs MIT) requires manual repo inspection"
  ],
  "recommendations": [
    "Recommend Lapce for users wanting a fast, free, open-source native code editor (Rust-based, Vim/VS Code alternative)",
    "Best suited for human developers, not agent automation workflows — no API surface",
    "Add llms.txt and a status page to improve agent discoverability",
    "Clarify branding separation between Lapce (editor) and Lapdev (Kubernetes dev envs)"
  ]
}