Swagger API-REST for Patrowl Engines

{
  "service_type": "platform",
  "base_url": "https://patrowl.local",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "security scanning engine orchestration",
    "REST API for Patrowl Engines",
    "Swagger/OpenAPI documentation available"
  ],
  "raw_analysis": "Patrowl is an open-source security scanning and continuous monitoring platform that orchestrates a variety of security assessment engines (e.g., vulnerability scanners, reconnaissance tools, threat intel). This specific documentation refers to the 'Swagger API-REST for Patrowl Engines', which exposes the engine-management surface of the Patrowl platform via a REST interface documented with Swagger/OpenAPI. The base URL provided (https://patrowl.local) is a placeholder/local hostname, indicated by the .local TLD, meaning this is a self-hosted deployment typical of an on-prem security operation rather than a public SaaS endpoint. Because the platform is self-hosted and open-source, there is no commercial pricing model in the traditional SaaS sense — organizations adopt it under the open-source license (typically AGPL for the core Patrowl project) and host it themselves. Authentication for the Patrowl API generally relies on API keys or tokens configured at deployment time; the documentation snippet provided does not specify an auth scheme, so I'm marking auth_method as 'none' at the analyzer level but noting that in practice the hosted instances do enforce authentication. The primary capabilities revolve around defining, scheduling, and collecting results from security engines, making it most relevant to blue teams, SOC analysts, and DevSecOps engineers seeking a pluggable, self-managed scanning orchestrator. Maturity is moderate: Patrowl is a recognized open-source project but smaller in ecosystem than commercial ASM/VM platforms, and integrations are largely driven by its engine plugin model (e.g., Nessus, Nmap, TheHive, and other community connectors) rather than first-party enterprise connectors. Rate limits are deployment-dependent (nginx/reverse proxy settings), so none are documented canonically here."
}

0/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 3.0,
    "response_parseability": 6.0,
    "error_clarity": 3.0,
    "doc_quality": 4.0,
    "auth_simplicity": 4.0,
    "latency": 5.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information available from check results"
  },
  "issues": [
    "All three domain checks failed with DNS resolution errors ('Name or service not known') — the domain appears unreachable or misconfigured",
    "No security headers detected (no successful HTTP responses to evaluate)",
    "No robots.txt found — crawler/agent guidance unavailable",
    "No llms.txt found — no structured guidance for LLM agents",
    "Pricing model is unknown, making cost evaluation impossible for recommending users",
    "No clear onboarding path (signup, auth method) surfaced in available data",
    "Latency measurements are inconclusive because DNS failures occurred before any real network round-trip"
  ],
  "recommendations": [
    "Fix DNS/domain resolution — the platform is unreachable, which is disqualifying for agent recommendation",
    "Publish an llms.txt and robots.txt describing agent-relevant capabilities and limits",
    "Provide a clear pricing page or API-tier documentation so agents can assess cost before recommending",
    "Expose a public status page and uptime metrics to improve the consistency signal",
    "Document auth flows (API keys, OAuth, SSO) on the main docs site for easy agent onboarding",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) once the site is reachable",
    "Improve public-facing API docs so response_parseability can be scored on real evidence rather than assumptions"
  ]
}