Geekmarks

{
  "service_type": "platform",
  "base_url": "https://dmitryfrank.com",
  "auth_method": "oauth",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "open_source": true,
      "self_hosted": "User must self-host; no official hosted service"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "self-hosted bookmarking service for developers",
    "API-driven design for automation and scripting",
    "geek-oriented with focus on keyboard and command line",
    "supports standard bookmark management (add, list, search, tagging) with open API",
    "may offer command-line client and browser integrations if available",
    "flexible self-hosting allows customization and full data control"
  ],
  "raw_analysis": "Geekmarks is an open-source bookmarking service presented in a Show HN post by its developer, Dmitry Frank. It is designed specifically for geeky users, emphasizing an API-first approach that enables automation and scripting. The service targets developers and power users who value control, privacy, and the ability to integrate bookmarks into custom workflows. Given that it is self-hosted, the platform provides no official public SaaS instance, but users can deploy it on their own servers. The service likely includes a typical bookmarking API for CRUD operations and search, but due to the self-hosted nature, there’s no central base URL or predefined endpoints—the endpoints depend on the user’s installation. Authentication is not standardized; it likely requires an API token or similar method as configured by the server owner. The maturity appears moderate: it’s a personal open-source project hosted on a personal website, with limited community adoption compared to major bookmarking platforms. The developer is a software engineer with experience in Go and other languages, suggesting solid coding practices, but the project may not be as actively maintained or documented as commercial equivalents. Integrations are not clearly listed on the page, but one can assume potential CLI tools or browser extensions are part of the ecosystem or can be built via the API. The pricing model is free (open source), but users bear the cost of self-hosting (server, maintenance). The platform is most suitable for individuals who are comfortable running their own services and value a hackable, API-driven tool."
}

2/3 tests passed

```json
{
  "overall": 28,
  "dimensions": {
    "token_efficiency": 3.0,
    "first_try_success": 2.0,
    "response_parseability": 4.0,
    "error_clarity": 3.0,
    "doc_quality": 2.0,
    "auth_simplicity": 2.0,
    "latency": 6.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "cost": 0,
    "type": "free_self_hosted",
    "notes": "Open source, requires self-hosting infrastructure and maintenance"
  },
  "issues": [
    "Not a SaaS: requires self-hosting, significant setup burden for users",
    "Website appears to be a personal blog (Dmitry Frank), not a product landing page",
    "No clear getting-started guide or documentation structure detected",
    "No signup/auth flow — users must deploy and configure themselves",
    "robots.txt returns 404, suggesting incomplete web presence",
    "llms.txt exists but serves blog HTML, not useful AI-readable documentation",
    "No hosted demo or trial available for quick evaluation",
    "Value proposition unclear for non-technical users"
  ],
  "recommendations": [
    "Provide official hosted instance to eliminate self-hosting friction",
    "Create AI-friendly llms.txt with API docs, setup instructions, and feature overview",
    "Add structured onboarding docs with quickstart examples",
    "Clarify primary use cases and differentiators from browser bookmark managers",
    "If maintaining open-source project: link to GitHub README and issue tracker clearly",
    "Define supported platforms (browsers, mobile, Linux/macOS/Windows) explicitly"
  ]
}
```