Void

{
  "service_type": "platform",
  "base_url": "https://voideditor.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "AI-powered code editor",
    "Open-source alternative to Cursor",
    "Local-first / privacy-friendly AI coding assistance",
    "VS Code fork / extension compatibility",
    "Multiple LLM provider support",
    "Code generation and editing via LLM"
  ],
  "raw_analysis": "Void (voideditor.com) is an open-source, AI-integrated code editor positioned as a free alternative to Cursor. It is a fork of VS Code, so it inherits the extension ecosystem, settings, and keybindings of VS Code. Void focuses on giving developers LLM-powered coding features (chat, inline edits, autocomplete) while emphasizing privacy, local model support, and the ability to connect directly to your own API keys for OpenAI, Anthropic, Ollama, and other providers rather than routing through a proprietary backend.\n\nMaturity: The project is relatively early-stage (launched publicly in 2024) but active on GitHub with a growing contributor community. It ships desktop builds for macOS, Windows, and Linux. It is aimed at individual developers and teams who want Cursor-like AI features without vendor lock-in or mandatory subscriptions.\n\nAPI: There is no public REST API for Void itself. The \"api\" categorization in the input likely reflects that Void *consumes* LLM APIs (OpenAI-compatible endpoints, etc.) rather than exposing one. Configuration is managed through the editor UI and local config files; provider credentials (API keys) are stored locally. There is no documented hosted service, no auth endpoint, and no rate limits to enumerate. Integration surface is primarily: (1) VS Code extensions, (2) OpenAI-compatible LLM endpoints, (3) Ollama / local model servers, and (4) MCP / tool-use style integrations as they are added.\n\nPricing: Void itself is free and open-source (Apache-2.0 at time of writing). Any cost comes from the underlying LLM provider the user chooses. This makes the pricing model effectively \"free\" for the editor, with BYO-key usage-based cost.\n\nCaveats: Because there is no first-party API and limited public documentation in this input, the endpoint list is empty and auth is \"none\" from a platform-access perspective. Further research would be needed to confirm current feature set, release cadence, and any enterprise offerings."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 4.0,
    "error_clarity": 4.0,
    "doc_quality": 4.5,
    "auth_simplicity": 6.0,
    "latency": 9.5,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "No pricing data available — likely free/open-source since it's positioned as an open-source Cursor alternative. Agent cannot confirm cost structure to users."
  },
  "issues": [
    "No pricing information surfaced — cannot answer cost questions for users",
    "Missing /llms.txt (404) — agents have no structured LLM-readable doc entry point",
    "No public API or structured data endpoints detected — code editor is GUI-first, hard for agents to drive or recommend programmatically",
    "Documentation quality unclear from probes; no help-center or getting-started signals found",
    "Authentication flow not observable — desktop download likely required, which is a friction point for agent-recommended onboarding",
    "No status page or reliability signal captured beyond a single fast 200"
  ],
  "recommendations": [
    "Publish /llms.txt with concise product value prop, pricing, platform support (Win/Mac/Linux), and LLM provider list",
    "Surface clear pricing/free-tier info on homepage so agents can answer cost questions",
    "Add a machine-readable sitemap/API docs if any programmatic config or extension marketplace access exists",
    "Document auth/onboarding steps (download size, account requirement) explicitly",
    "Provide compatibility matrix (VS Code extension support) as structured data",
    "Publish uptime/status endpoint to strengthen consistency signal for agent recommendations"
  ]
}