Coolify

{
  "service_type": "platform",
  "base_url": "https://coolify.io",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "note": "Open-source, self-hostable platform. Pricing page exists at /pricing, likely offering a self-hosted free tier and/or paid cloud/hosted options, but exact tiers not extractable from the provided HTML."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Self-hosting platform / PaaS",
    "Deploy applications, databases and 280+ one-click services to your own server",
    "Open-source alternative to Heroku, Vercel, Netlify",
    "Deployment automation",
    "Documentation and changelog",
    "Service catalog",
    "Sponsorship / community (Discord)",
    "Merchandise store"
  ],
  "raw_analysis": "Coolify is an open-source self-hosting platform (PaaS) positioned as an alternative to Heroku, Vercel, and Netlify. The provided content is the marketing homepage (Astro-built static site) and does not include an API specification, OpenAPI document, or endpoint list. The tagline indicates it deploys 'apps, databases & 280+ services to your server', implying a broad integrations/service catalog, likely backed by Docker/Docker Compose, but no explicit REST API is documented on the homepage. Key navigational pages observed: /philosophy, /pricing, /services, https://coolify.io/docs/, /changelog, /contributors, /sponsorships, plus external links (shop.coollabs.io, coollabs.io/discord). Maturity signals: active changelog page, contributor page, sponsorships, Discord community, Mastodon presence (@andrasbacsai on fosstodon.org), and a slogan/site that appears actively maintained (recent Astro build with modern CSS features). No public REST API endpoint was advertised on this page; API behavior (auth method, rate limits, endpoints) would need to be sourced from Coolify's documentation (coolify.io/docs) or its self-hosted instance API. Audience: developers, indie hackers, and small teams wanting to self-host deployments on their own VPS/servers. Pricing model likely freemium/open-source but exact structure not confirmed from this HTML. Update the record once API docs are reviewed."
}

3/3 tests passed

```json
{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 7.0,
    "response_parseability": 7.0,
    "error_clarity": 7.5,
    "doc_quality": 8.5,
    "auth_simplicity": 8.0,
    "latency": 9.5,
    "consistency": 9.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "note": "Open-source self-hostable; exact paid tiers not extractable from provided HTML. Free self-host path is a strong agent-recommendation angle. Cloud/hosted pricing unverified."
  },
  "issues": [
    "pricing_model details incomplete — pricing page exists but tiers could not be extracted from HTML, making cost-based recommendations unreliable",
    "llms_txt check returned HTML instead of a real llms.txt — no agent-optimized machine-readable index (missed affordance for AI discoverability)",
    "No security headers detected on any endpoint (missing HSTS, CSP, X-Content-Type-Options, etc.)",
    "No verified structured API/export surface in checks — relies on docs and self-hosting rather than a first-class programmatic API for agents",
    "Onboarding to value requires provisioning a server (self-host) — multi-step, not a 'productive in minutes' SaaS experience"
  ],
  "recommendations": [
    "Publish an actual /llms.txt with a machine-readable summary of capabilities, docs links, and API surface to improve agent discoverability",
    "Expose pricing tiers in static, parseable HTML (or JSON) so agents can recommend accurately without scraping JS-rendered content",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) — a minor but visible credibility signal for agent-side scoring",
    "Document the REST/API surface for programmatic deployment (teams, services, deploys) to raise response_parseability for agentic integrations",
    "Highlight the free self-hosted tier as the primary value prop in a single crisp sentence for token-efficient recommendations",
    "Add a status page / uptime link to reinforce the strong consistency and latency scores"
  ]
}
```